MediaPad M5 Lite (BAH2-W19) is not booting after flashing custom rom - Huawei MediaPad M5 Lite ROMs, Kernels, Recoveries,

MediaPad M5 Lite (BAH2-W19) is not booting after flashing custom rom - Huawei MediaPad M5 Lite ROMs, Kernels, Recoveries,

Hi there.
I screwed up my MediaPad M5 Lite (Wifi edition: BAH2-W19, EMUI 8 installed. It's a treble compatible device) yesterday and need help.
I did the following steps before it all went down the gutter:
1. I successfully unlocked the bootloader using the DC Unlocker method
2. I downloaded the latest a-only AOSP release of "phhusson AOSP 9.0 v119": system-arm64-aonly-vanilla-nosu.img.xz (https://github.com/phhusson/treble_experimentations/releases)
3. I rebooted into bootloader and flashed the unzipped .img file to the device. The flash was successful as all 4 steps of copieing stuff tot he system partition said "OKAY"
4. now I used "fastboot reboot" and the trouble started. The tablet froze in fastboot mode. It just didn't restart.
5. I turned it of using a long push on the power button. Then it restarted and got stuck at the start screen. I'll attach a screenshot so you know what I am seeing.
6. From now on I was only able to boot into fastboot mode and into the stock recovery. There I did factory reset and cache formatting several times but with no effect.
7. Only thing that still worked was the eRecovery function in the EMUI stock recovery. With this I was able to download some official firmware from Huawei automatically and the tablet was back to stock
8. This night the OS did an auto update to v215.
9. So this morning I repeated the step 2. from above but with a different a-only custom rom and again it didn't work out
10. I tried to use the eRecovery function to get back to stock, but now the recovery is broken and throws an error "Getting package info failed".
I also tried to download older firmware from https://androidhost.ru/ and flash it with the dload method. Without success of course. While doing it I receive an error "Software install failed!". I will attach a screenshot.
Can anybody give me a hint what I could do next to approach the problem?
Best
rob

Well, you didn't had TWRP as recovery, so no nandroid backup available. From one of my experiences with flashing a stock rom for acer, I had to delete some lines of code from the meta inf folder relating the version of the phone, in order to successfully flash it. Maybe the stock ROM you are trying has some lines of code detecting if bootloader unlocked.

Im also having trouble getting a good tutorial for getting rid of the os or just to have magisk on the tablet

You dowoad latest rom and flash stock via hru and. Twrp search xda

unbrick Huawei MediaPad M5 Lite
r0b said:
Hi there.
I screwed up my MediaPad M5 Lite (Wifi edition: BAH2-W19, EMUI 8 installed. It's a treble compatible device) yesterday and need help.
I did the following steps before it all went down the gutter:
1. I successfully unlocked the bootloader using the DC Unlocker method
2. I downloaded the latest a-only AOSP release of "phhusson AOSP 9.0 v119": system-arm64-aonly-vanilla-nosu.img.xz (https://github.com/phhusson/treble_experimentations/releases)
3. I rebooted into bootloader and flashed the unzipped .img file to the device. The flash was successful as all 4 steps of copieing stuff tot he system partition said "OKAY"
4. now I used "fastboot reboot" and the trouble started. The tablet froze in fastboot mode. It just didn't restart.
5. I turned it of using a long push on the power button. Then it restarted and got stuck at the start screen. I'll attach a screenshot so you know what I am seeing.
6. From now on I was only able to boot into fastboot mode and into the stock recovery. There I did factory reset and cache formatting several times but with no effect.
7. Only thing that still worked was the eRecovery function in the EMUI stock recovery. With this I was able to download some official firmware from Huawei automatically and the tablet was back to stock
8. This night the OS did an auto update to v215.
9. So this morning I repeated the step 2. from above but with a different a-only custom rom and again it didn't work out
10. I tried to use the eRecovery function to get back to stock, but now the recovery is broken and throws an error "Getting package info failed".
I also tried to download older firmware from https://androidhost.ru/ and flash it with the dload method. Without success of course. While doing it I receive an error "Software install failed!". I will attach a screenshot.
Can anybody give me a hint what I could do next to approach the problem?
Best
rob
Click to expand...
Click to collapse
Unbrick using Huawei Multi tool .
---------- Post added at 03:14 PM ---------- Previous post was at 03:10 PM ----------
r0b said:
Hi there.
I screwed up my MediaPad M5 Lite (Wifi edition: BAH2-W19, EMUI 8 installed. It's a treble compatible device) yesterday and need help.
I did the following steps before it all went down the gutter:
1. I successfully unlocked the bootloader using the DC Unlocker method
2. I downloaded the latest a-only AOSP release of "phhusson AOSP 9.0 v119": system-arm64-aonly-vanilla-nosu.img.xz (https://github.com/phhusson/treble_experimentations/releases)
3. I rebooted into bootloader and flashed the unzipped .img file to the device. The flash was successful as all 4 steps of copieing stuff tot he system partition said "OKAY"
4. now I used "fastboot reboot" and the trouble started. The tablet froze in fastboot mode. It just didn't restart.
5. I turned it of using a long push on the power button. Then it restarted and got stuck at the start screen. I'll attach a screenshot so you know what I am seeing.
6. From now on I was only able to boot into fastboot mode and into the stock recovery. There I did factory reset and cache formatting several times but with no effect.
7. Only thing that still worked was the eRecovery function in the EMUI stock recovery. With this I was able to download some official firmware from Huawei automatically and the tablet was back to stock
8. This night the OS did an auto update to v215.
9. So this morning I repeated the step 2. from above but with a different a-only custom rom and again it didn't work out
10. I tried to use the eRecovery function to get back to stock, but now the recovery is broken and throws an error "Getting package info failed".
I also tried to download older firmware from https://androidhost.ru/ and flash it with the dload method. Without success of course. While doing it I receive an error "Software install failed!". I will attach a screenshot.
Can anybody give me a hint what could do next to approach the problem?
dnrob
Click to expand...
Click to collapse
You can install these roms only if you can downgrade to update v177 and lower

Like me you need to Unbrick your mediapad m5 lite
First place need to go back in Fastboot mode.
So UNPLUG , turn off , wait a second and turn on with volume Down , when screen blink release power button and keep volume down pressed a second until Fastboot mode
Or, try to boot in Fastboot with volume down + power AND USB plugged in goes into fastboot, or TWRP if you flashed TWRP to RECOVERY2 instead to RECOVERY.
If doesnt work try the same plug or unplug cuz we have Recovery_ramdisk , eRecovery and eRecovery2
WHEN its okay and you can turn on fastboot mode
Second prepair the img's for unbricking
The LEGIT methods its come back stock rom , then you'll be able to do what you want.
Download Huawei Multi-Tools , Huawei Update Extractor and update.zip of your stock ROM and update_data_full
Then use Huawei Update Extractor to extract
system.img ramdisk.img recovery_ramdisk.img From update.app\update.zip and
Cust.img from update.app\update_full_public.zip.
If you have backup of your userdata.img its the time to put all together in the same directory before go futher.
If all its good , you just need to click unbrick.
Maybe i'll soon do a guide for unbrick and prevent brick , and how install twrp without losing data or encryption data
helmuth said:
And just for the complete list:
Volume up + power AND USB plugged in goes into eRecovery (or TWRP, if you flashed TWRP to RECOVERY2 instead to RECOVERY)
Volume up and down + power and USB plugged in forces update via USB (indicated by a little USB-like icon in the recovery circle. The progess bar goes to 5% and waits for input from your PC)
Click to expand...
Click to collapse

RAMDISK238.img, Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip and twrp8.img you will find at
android-hilfe.de->forum huawei-mediapad-m5-lite -> custom-roms-mediapad page-5
Theese custom roms should work:
Andy Yan's LineageOS 17 (Android 10) -> lineage-17.0-20191231-UNOFFICIAL-treble_arm_avN.img.xz
Pierre-Hugues Husson AOSP 10.0 v209 -> system-quack-arm64-aonly-vanilla.img.xz
Following this guide you will loose all your data so be sure to have a backup
This should work for a Mediapad M5 lite BAH2-W19OCEC432-238
Precondition: Unlocked Bootloader / OEM Unlocked / USB Debugging active
1. if you brick your device don`t blame me
2. check, if the version B238 is installed
3. back up your data
4. copy Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip on SD card
Fastboot:
5. boot into Fastboot Mode.
6. flash TWRP -> fastboot flash recovery_ramdisk twrp8.img
7. fastboot reboot recovery (the first time booting should show up the twrp menu)
if the boot message "2. Press Volume up for 3 seconds" appears must do a Factory Reset in the Stock Recovery. After a reboot the TWRP menu shows up. In lineageos you can activate advanced reboot in developer settings to boot in TWRP menu by pressing recovery mode
TWRP:
8. Wipe -> Advanced Wipe -> select data + cache + dalvik-cache -> Swipe to wipe -> back to start menu
9. Install -> Select Storage -> select Mircro SD card -> OK -> select Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip -> Swipe to confirm Flash
10. Reboot -> Bootloader (not System!!!)
Fastboot:
11. fastboot flash ramdisk RAMDISK238.img
12. fastboot flash system lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img
(or AOSP 10.0 v209)
13. fastboot reboot
LineageOS should start.
other custom roms could work as well.......
Edit:
There´s a new version of LineageOS available:
https:######sourceforge.net###projects###andyyan-gsi###files###lineage-17.x###lineage-17.1-20200111-UNOFFICIAL-treble_arm64_avN.img.xz###download
replace ### with /
It works well on my m5lite

It did not work on B239
I am trying now to get back to the stock rom.
I think the problem is with RAMDISK238.img :/
Do you know how to get one for 239?
Thanks !
BesterTrainer said:
RAMDISK238.img, Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip and twrp8.img you will find at
android-hilfe.de->forum huawei-mediapad-m5-lite -> custom-roms-mediapad page-5
Theese custom roms should work:
Andy Yan's LineageOS 17 (Android 10) -> lineage-17.0-20191231-UNOFFICIAL-treble_arm_avN.img.xz
Pierre-Hugues Husson AOSP 10.0 v209 -> system-quack-arm64-aonly-vanilla.img.xz
Following this guide you will loose all your data so be sure to have a backup
This should work for a Mediapad M5 lite BAH2-W19OCEC432-238
Precondition: Unlocked Bootloader / OEM Unlocked / USB Debugging active
1. if you brick your device don`t blame me
2. check, if the version B238 is installed
3. back up your data
4. copy Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip on SD card
Fastboot:
5. boot into Fastboot Mode.
6. flash TWRP -> fastboot flash recovery_ramdisk twrp8.img
7. fastboot reboot recovery (the first time booting should show up the twrp menu)
if the boot message "2. Press Volume up for 3 seconds" appears must do a Factory Reset in the Stock Recovery. After a reboot the TWRP menu shows up. In lineageos you can activate advanced reboot in developer settings to boot in TWRP menu by pressing recovery mode
TWRP:
8. Wipe -> Advanced Wipe -> select data + cache + dalvik-cache -> Swipe to wipe -> back to start menu
9. Install -> Select Storage -> select Mircro SD card -> OK -> select Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip -> Swipe to confirm Flash
10. Reboot -> Bootloader (not System!!!)
Fastboot:
11. fastboot flash ramdisk RAMDISK238.img
12. fastboot flash system lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img
(or AOSP 10.0 v209)
13. fastboot reboot
LineageOS should start.
other custom roms could work as well.......
Edit:
There´s a new version of LineageOS available:
https:######sourceforge.net###projects###andyyan-gsi###files###lineage-17.x###lineage-17.1-20200111-UNOFFICIAL-treble_arm64_avN.img.xz###download
replace ### with /
It works well on my m5lite
Click to expand...
Click to collapse

sasuke988 said:
It did not work on B239
I am trying now to get back to the stock rom.
I think the problem is with RAMDISK238.img :/
Do you know how to get one for 239?
Thanks !
Click to expand...
Click to collapse
https://
pro-teammt.ru/
en/
online-firmware-database/
?firmware_model=BAH2-W19&firmware_page=0
Check out your model (C432C431/...)
Use the huawei extractor to extract the images

Can someone check if this is legit? https://romprovider.com/2019/09/9-1-0-151-b151-firmware-jordan2-l09b/amp/

Raresh T said:
Can someone check if this is legit? https://romprovider.com/2019/09/9-1-0-151-b151-firmware-jordan2-l09b/amp/
Click to expand...
Click to collapse
It's for the 8" screen variant. It won't work on our 10.1"

is there any current custom house for this model because no links work. And on the stock, I have a problem with 5ghz Wi-Fi

You'd better install TWRP,flash FBE-disabler and format data partition
Anyway,firmware can be found at professorjtj.github.io and I recommend you rebrand and update it to EMUI9 to get better treble compatibility

SkipM4 said:
You'd better install TWRP,flash FBE-disabler and format data partition
Anyway,firmware can be found at professorjtj.github.io and I recommend you rebrand and update it to EMUI9 to get better treble compatibility
Click to expand...
Click to collapse
thats an interesting suggestion. could you post some guides on how could someone rebrand their device ?

Related

Asus ZenPad 8.0 (Z380KL) Information Repository

Just going to dump all the info I've found about this device into this thread. All the threads pertaining to this thread are in Russian and I can't read Russian, so this might be helpful to any English speaking owners of this tablet.
Special thanks to Telegram user @SSDD_1744 (don't know your XDA/Reddit user, I'm sorry) for basically spoonfeeding me all these instructions!
WARNING: If you need to flash to stock for whatever reason, be sure to download a image file specific to your country. If you don't, you'll hard brick your device that can only be fixed QPST (supposedly).
Rooting:
(Tested on 5.0.2)
Install KingRoot. Let it root your device.
Install Super-SU Me, to get rid of the bloatware that comes with KingRoot.
Installing Xposed:
I used Flashify to flash TWRP. Be sure to flash the right version though (2.8.7.7 v2) or else you won't be able to mount cache.
Then download Xposed (version sdk21 ARM) and flash it.
WARNING: Flash v1 of the modded TWRP and you won't be able install any apps after flashing Xposed.
Unbricking:
Still working on it. Downloaded QPST but have not been able to get QPST 2.7 to read the tablet.

Links:
Discussion:
https://translate.googleusercontent...690491&usg=ALkJrhiWSlkbZ-tUofZx68NPSGIv8pjIPA
Root:
https://translate.googleusercontent...JrhhQszcRvUo8HILThvz57JmsLj4L9g#entry44556703
https://translate.googleusercontent...JrhiCt__6apcRhk-gtcBExYJCnC9nGQ#entry41676452
Instructions for obtaining the rights to Ruth phones / tablets.
Tested on Android 4.4+
perhaps this algorithm works on Android 5+, I have no way to verify
All transactions with their phones / tablets are performing at your own risk !!!
To get started, read this post from start to finish and only then proceed to action!
Introduction
This instruction is written based on my own experience obtaining root on their plates, and then on the Xperia M2, bought plemyashki. For instructions attached versions of applications that were relevant at the time, the new version can download the relevant topics on the forum, there will find all information on how to work with the proposed programs and algorithms for their actions (links to topics added).
For all the action with your phone / tablet you are responsible for yourself!
Download all the necessary tools to obtain Root (of instructions / topics on the forum), obespechte for phone / tablet access to the Internet (Wi-F / mobile data) and let the phone settings / tablet installation from unknown sources.
Needed Downloads
KingRoot_V4.5.0B202.apk (6.76 MB)
Me_5.9.apk-SuperSU (9.07 MB)
V2.49 Beta.apk SuperSU (5.63 MB)
eu.chainfire.supersu.pro.205.apk (52,88 KB)
Next in series:
1. Install KingRoot .
Get Ruth's right, in the device may reboot.
2. Set SuperSU-Me, .
Run the grantor, the program deletes KingRoot and Chinese KingUser with replacement SuperSu.
Remove the longer SuperSu-Me the desired program.
3. Obnovyaem SuperSu to the latest version. Then set PRO-key .
Installing Pro-key Optionally !!! Use Cases SuperSu without installing key .
4. Open SuperSu and on-demand update binary SU normal way. After a successful update, confirm the request to restart.
5. To make sure that everything is done correctly, check the correct installation and operation of Ruth (mount the system partition on the record), I used the Root Checker Pro and Root Explorer , respectively.
The output is a complete rut without kitayschiny with SuperSu Pro. We use and enjoy
Click to expand...
Click to collapse
Unlocking bootloader (haven't tried this):
https://translate.googleusercontent...Jrhh6g4wI-8Hb_LzAcPnIUxYvWNzZ0A#entry46711087
Stock firmware:
https://translate.googleusercontent...?s=&showtopic=703414&view=findpost&p=45272695

Damn, development has really boomed on this little tablet! Finally got it back after a few months (I sent it into Asus to repair it for me).
Stock ROM:
https://www.asus.com/ru/Tablets/ASUS_ZenPad_80_Z380KL/HelpDesk_Download/ (I can't get the English version to load, delete the /ru/ and you'll be redirected to the English site)
https://www.asus.com.cn/Tablets/ASUS_ZenPad_80_Z380KL/HelpDesk_Download/ (Chinese site)
==== REMEMBER TO DOWNLOAD THE CORRECT COUNTRY OR YOU'LL BE BRICKED) ====
https://yadi.sk/d/b1NMLXHBsNV8C (latest software for the worldwide model)
[http://4pda.ru/forum/index.php?showtopic=703414&st=320#entry50270292]
http://4pda.ru/forum/index.php?showtopic=703414&st=200#entry49389176 (Asus Flash Tool and stock ROM v4.8.2 WW [WorldWide])
Unlocking bootloader:
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48200665 (use fastboot oem device-info to check if it's unlocked)
Root:
http://4pda.ru/forum/index.php?showtopic=690491&st=580#entry44778545 (KingRoot - you'll need a 4PDA.ru account to download this)
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48185323 (last section of the post)
CM13:
http://get.cm/?device=P024&type=nightly
https://vasy.ru/CM13/
http://forum.xda-developers.com/android/help/asus-zenpad-8-z380kl-custom-rom-t3370277
http://forum.xda-developers.com/android/development/kernel-asus-z380kl-p024-kcal2-t3405595 (Kernel)
Recovery:
https://vasy.ru/TWRP/P024/
http://4pda.ru/forum/index.php?showtopic=690491&st=1220#entry48094504 (TWRP 2.8.7.0)
http://forum.xda-developers.com/android/help/asus-zenpad-8-0-z380kl-bootloop-t3373051
Guides:
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48185323 (this has a lot of instructions: root, recovery, boot partition restore, adb drivers etc.)
http://forum.xda-developers.com/android/help/asus-zenpad-8-0-z380kl-bootloop-t3373051 (this has a bunch of files, Resurrection Remix [I haven't tested it yet tho], and instructions on getting out a bootloop)
http://4pda.ru/forum/index.php?showtopic=690491&st=1640#entry49724823 (flashing stock software)
If you want to open the engineering menu, type " * # * # 4636 # * # * "
To boot into fastboot, restart/turn on the device and hold volume up. It'll pop you into a menu with three options.
To boot into recovery, from the fastboot screen (three options), use the volume buttons and navigate to the second option "factory reset" and hit power to confirm. It'll boot into recovery.
=====================================================================================
Recommended way to flash ROMs:
1) Download TWRP. Use adb to boot (NOT flash) into TWRP. Flash ROM there.
2) use KingRoot to root. Use Flashify to flash the ROM.
======================================================================================
If you want to go look up some more info or guides, go here:
http://4pda.ru/forum/index.php?act=...=rel&subforums=0&query=z380kl&forums=570&st=0
and use GTranslate to translate the page. The first page is the earliest posts with the keyword, the last page are the latest post.

please add these ROM's for this Device:
Ressurection Remix:
https://www.androidfilehost.com/?w=files&flid=121811
AICP 12.1:
https://www.androidfilehost.com/?w=files&flid=136181

The latest Official ROM P024 model:
http://dlcdnet.asus.com/pub/ASUS/Ee...ser.zip?_ga=1.109506565.1670552787.1483182775
ZenPad 8 Z380KL Firmware: V5.9.0.0 (WW SKU version only)
Improved Item:
1. Update Google security patch
2. Support unlock tool

9008 brick info:
https://4pda.ru/forum/index.php?showtopic=643084
Pertaining to p024:
https://4pda.ru/forum/index.php?showtopic=643084&st=5740
https://4pda.ru/forum/index.php?showtopic=643084&st=3660 (page 179 - 180, 183 - 185 discusses the files needed to unbrick and how you would - CTRL + F Russ and read the people who quote him)
How I bricked: https://4pda.ru/forum/index.php?showtopic=703414&st=180#entry49329798
https://4pda.ru/forum/index.php?showtopic=690491&st=1420#entry48527044 (unbricking files - dead link though)
https://4pda.ru/forum/index.php?showtopic=703414&st=140 (discussing how to fix using the images from the dump)

I see that Lineage OS is supported on Z380KL. However, I found the wiki spec showing Snapdragon 410, but I found Z380KL in Asia with Snapdragon 615. Before I commit, I'd like to know if anyone knows whether LineageOS is fully compatible with Z380KL with Snapdragon 615 chipsets? Thanks.

Special thanks to @a350tv for helping me comb through 4PDA - this process would've been a lot slower or just wouldn't have happened if he hadn't offered to translate guides and download links to me. So most of the credit goes to him.
Flashing TWRP on 6.0.1 (Sept 1, 2016 patch):
1) grab your drivers (W10: boot into "no driver signature verification mode" to install the drivers needed for fastboot)
https://drive.google.com/open?id=1cGcoDCvmTxfXWNTG0iOXHw1WScmYBrKS
2) turn on debugging
3) type in "adb devices", verify that your computer sees your tablet (if you don't have ADB/Fastboot, get https://forum.xda-developers.com/showthread.php?t=2317790)
4) type in "adb reboot bootloader"
5) you'll see three options: 1. Enter SD DL mode, 2. Factory Reset, 3. Exit update mode
6) type in "fastboot devices", verify that your computer sees your tablet
7) grab your TWRP file (http://vasy.ru/TWRP/P024/) and type in "fastboot flash recovery [replace w/ location of the TWRP file].img"
8) once it says "finished", click factory reset mode (use volume buttons to navigate, power button to enter)
9) it should reboot into TWRP, slide to allow modifications
10) Boom, TWRP is installed.
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
IF YOU WANT TO KEEP TWRP BUT DON'T WANT Magisk:
1) After first boot into TWRP, turn off tablet.
2) Then turn on and hold Volume Up + Power. That will boot you into Bootloader Mode.
3) Go into factory reset and it should boot you into TWRP.
Now, it's safe to boot into the OS.
(TL;DR: Boot into TWRP twice before booting into the OS or else stock recovery will overwrite TWRP.)
Flashing LineageOS:
1) DL LOS from https://download.lineageos.org/P024
2) DL GApps from http://opengapps.org/ (choose 7.1)
3) boot into TWRP
4) go into Wipe, slide to wipe
5) go to Install, click on LOS file > add to queue, click on Open GApps file > add to queue, flash
6) wait til it's done, click "reboot"
7) wait a while (took mine 3 or so minutes to boot)
8) enjoy!
My GDrive folder with all files needed (except ROM and GApps)
https://drive.google.com/open?id=0BzJ-WWaQYXttTkttdHNELVBEc2M
To do:
Use this tutorial to backup all my partitions, just in case I get bricked yet again.
https://forum.xda-developers.com/showthread.php?t=2450045
Links to unbrick device via Asus FlashTool
Links to service ROMs (for use with AFT)
Add original links from 4PDA

ROMs
LineageOS: https://download.lineageos.org/P024
AICP: https://saki-sss.blogspot.com.by/2016/12/z380k-aicp-121.html
Resurrection Remix: https://androidfilehost.com/?w=files&flid=121811
(made by https://androidfilehost.com/?w=profile&uid=457095661767100043, found from http://andmem.blogspot.jp/2016/05/asus-zenpad-8-z380kl-root-rom.html#chapter-19) - abandoned?

seities said:
I see that Lineage OS is supported on Z380KL. However, I found the wiki spec showing Snapdragon 410, but I found Z380KL in Asia with Snapdragon 615. Before I commit, I'd like to know if anyone knows whether LineageOS is fully compatible with Z380KL with Snapdragon 615 chipsets? Thanks.
Click to expand...
Click to collapse
probably not. I think it's only compatible with the SD 410.

xDark_ said:
Special thanks to @a350tv for helping me comb through 4PDA - this process would've been a lot slower or just wouldn't have happened if he hadn't offered to translate guides and download links to me. So most of the credit goes to him.
Flashing TWRP on 6.0.1 (Sept 1, 2016 patch):
1) grab your drivers (W10: boot into "no driver signature verification mode" to install the drivers needed for fastboot)
https://drive.google.com/open?id=1cGcoDCvmTxfXWNTG0iOXHw1WScmYBrKS
2) turn on debugging
3) type in "adb devices", verify that your computer sees your tablet (if you don't have ADB/Fastboot, get https://forum.xda-developers.com/showthread.php?t=2317790)
4) type in "adb reboot bootloader"
5) you'll see three options: 1. Enter SD DL mode, 2. Factory Reset, 3. Exit update mode
6) type in "fastboot devices", verify that your computer sees your tablet
7) grab your TWRP file (http://vasy.ru/TWRP/P024/) and type in "fastboot flash recovery [replace w/ location of the TWRP file].img"
8) once it says "finished", click factory reset mode (use volume buttons to navigate, power button to enter)
9) it should reboot into TWRP, slide to allow modifications
10) Boom, TWRP is installed.
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
IF YOU WANT TO KEEP TWRP BUT DON'T WANT Magisk:
1) After first boot into TWRP, turn off tablet.
2) Then turn on and hold Volume Up + Power. That will boot you into Bootloader Mode.
3) Go into factory reset and it should boot you into TWRP.
Now, it's safe to boot into the OS.
(TL;DR: Boot into TWRP twice before booting into the OS or else stock recovery will overwrite TWRP.)
Flashing LineageOS:
1) DL LOS from https://download.lineageos.org/P024
2) DL GApps from http://opengapps.org/ (choose 7.1)
3) boot into TWRP
4) go into Wipe, slide to wipe
5) go to Install, click on LOS file > add to queue, click on Open GApps file > add to queue, flash
6) wait til it's done, click "reboot"
7) wait a while (took mine 3 or so minutes to boot)
8) enjoy!
My GDrive folder with all files needed (except ROM and GApps)
https://drive.google.com/open?id=0BzJ-WWaQYXttTkttdHNELVBEc2M
To do:
Use this tutorial to backup all my partitions, just in case I get bricked yet again.
https://forum.xda-developers.com/showthread.php?t=2450045
Links to unbrick device via Asus FlashTool
Links to service ROMs (for use with AFT)
Add original links from 4PDA
Click to expand...
Click to collapse
Thanks for the tutorial, I had already dared to flash twrp recovery before you wrote this tutorial...
I believe my bootloader is still locked. And I could not reproduce/ write exactly what I did. But, in my case, just for information, when I want to go back into twrp, I can boot into bootloader (power volume up) and then option 2 reset the device gives me the twrp... I am not sure if that is how you get it, but for me, I still had twrp.
I think i will install magisk after reading your post.

jutphaas said:
Thanks for the tutorial, I had already dared to flash twrp recovery before you wrote this tutorial...
I believe my bootloader is still locked. And I could not reproduce/ write exactly what I did. But, in my case, just for information, when I want to go back into twrp, I can boot into bootloader (power volume up) and then option 2 reset the device gives me the twrp... I am not sure if that is how you get it, but for me, I still had twrp.
I think i will install magisk after reading your post.
Click to expand...
Click to collapse
I don't think unlocking the BL is necessary for flashing LOS. But yes, that's how I get into TWRP as well.

Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.

pucci2 said:
Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.
Click to expand...
Click to collapse
Can you still access fastboot, then at least you can flash twrp as described before in this thread and install from twrp lineageos p024 (lineage-14.1-20180105-nightly-P024-signed.zip) and Open gapps to get google playstore etc , select Arm, (not 64) then version 7.1, then Pico would work.
If you have twrp, you at least can still use your asus... I have found no way to flash original stock... stock must not be flashed from twrp.
Since you mention twrp already used, you can try: turn your device off, then press volume up then the bootloader menu comes, select 2: reset to enter twrp(where it says reset. if you had flashed twrp, that is how you can get into twrp) from there, install lineage os and gapps from micro sd card
My rom is MMB29M.WW_P024-V5.9.4-20170613

xDark_ said:
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
Click to expand...
Click to collapse
I assume this is on stock rom ? What version of magisk would work? I found I can be back at stock with my twrp backup so ..
But magisk 15.3 zip failed to install on stock-
I also used supersu v82 working on stock, or lineageos.
Would you know what magisk works on lineageos?
I like the exsd extension of magisk so I would like to try it on this device, either stock or lineageos

jutphaas said:
I assume this is on stock rom ? What version of magisk would work? I found I can be back at stock with my twrp backup so ..
But magisk 15.3 zip failed to install on stock-
I also used supersu v82 working on stock, or lineageos.
Would you know what magisk works on lineageos?
I like the exsd extension of magisk so I would like to try it on this device, either stock or lineageos
Click to expand...
Click to collapse
Yes it was. I flashed 15.2 on both stock and LOS. I've heard of some issues with 15.x so you can try .2 or 14.x.

pucci2 said:
Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.
Click to expand...
Click to collapse
What error was given? What do you see when you connect it to a computer? What does "tablet locked" mean? Would help if you gave some pictures too.
I'm currently in the process of getting the RAW files/service ROMs for AFT but I don't have an ETA on when I'll be able to get that.

No on the tablet I have not installed TWRP and no other recovery.When I go into the original recovery of the tablet there is always the screen with the lock closed at the bottom right and there is no way to show it to the PC even with adb sideload, l 'only program that recognizes me the tablet is Asus flash tool, however, as I have already written the damn ROM in RAW format is untraceable.

pucci2 said:
No on the tablet I have not installed TWRP and no other recovery.When I go into the original recovery of the tablet there is always the screen with the lock closed at the bottom right and there is no way to show it to the PC even with adb sideload, l 'only program that recognizes me the tablet is Asus flash tool, however, as I have already written the damn ROM in RAW format is untraceable.
Click to expand...
Click to collapse
Does it respons to adb devices of fastboot devices in this stage?

no, it is not recognized

[Guide] How to install custom ROM (Tested with Pixel Experience and Lineage OS)

I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!

thanks so much for this! Been flashing since andriod 1.6 but couldnt wrap my dumb head around these dual partitions.

And is the same for miui.eu ?

raphae34 said:
And is the same for miui.eu ?
Click to expand...
Click to collapse
No. Follow the instructions in the OP there. They work.

Kaissner said:
I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!
Click to expand...
Click to collapse
The 1st method for Pixel Experience does not work for me, after following all the steps carefully, if i boot into system it boots me to fastboot everytime, or if I dont reboot to system (in TWRP after flashing everything) it only says no OS installed are you sure you want to continue, so any help?

Snjeky said:
The 1st method for Pixel Experience does not work for me, after following all the steps carefully, if i boot into system it boots me to fastboot everytime, or if I dont reboot to system (in TWRP after flashing everything) it only says no OS installed are you sure you want to continue, so any help?
Click to expand...
Click to collapse
the "no os installed" is normal, dont worries.
The installation method for pixel experience worked when I installed the old version, it was updated multiple times so probably the process changed, I will update the thread later

This dual slot fuking my mind up.
TWRP asking for password to decrypt data. while first boot in recovery.
also *unable to decrypt FBE device* error while formating data.
"couldnt able to flash Any ROM "unable to partition path/cache" error.
ps. flashed in slot a.

When I install twrp on fastboot it stuck there, I have Android 10 stock, is anything that I can do ? I try like 3 times and always the same

ManuMan99 said:
When I install twrp on fastboot it stuck there, I have Android 10 stock, is anything that I can do ? I try like 3 times and always the same
Click to expand...
Click to collapse
downgrade to android 9. apparently android 10 got some issues.

pradie said:
downgrade to android 9. apparently android 10 got some issues.
Click to expand...
Click to collapse
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade

garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
I apologize for not being precise. i had the same issue. downloaded and flashed android 9 Stock global ROM with mi flash tool. now it's booted correctly.
---------- Post added at 12:37 PM ---------- Previous post was at 12:37 PM ----------
garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
I apologize for not being precise. i had the same issue. downloaded and flashed android 9 Stock global ROM with mi flash tool. now it booted correctly.

Sapper Morton said:
Indeed, it's not as straight forward, but it's possible without losing Widevine L1 security level; read my experience here, I explained the steps I took ; so far, I came back to v11.0.8.0 QFQMIXM from v10.3.17.0 PFQEUXM after the downgrade, with no issues whatsoever (no format/wipe data); my DRM Keys and sensors remains intact.
Click to expand...
Click to collapse
Thank you I wouldn't have guessed that would work it seems too easy to be a fix but that's good news.
Thanks for that info

garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
Then what to do? I downgraded from Android 10 Stock to Android 9 Stock 3.13.0.PFQMIXM because I soft-bricked my phone. I Flashed the stock ROM using Mi Flash tool. It flashed OK but my MI A3 sensors are not working. Someone said Flash persist.img via TWRP but when I try to flash it asked me in which partition to flash.
Partitions available are:
bluetooth
modem
System Image
Dtbo
Vendor Image
splash
Boot
Install Recovery Ramdisk
I am confused where to flash. If this method isnt suitable as you said then guide me what to do. I have Global Fastboot ROM for Android 9 Version 3.16.0.PFQMIXM for Mi A3 available. Should I flash this using Mi Flash tool? Does it solve sensor issues or not? Please help.

vjrx88 said:
Then what to do? I downgraded from Android 10 Stock to Android 9 Stock 3.13.0.PFQMIXM because I soft-bricked my phone. I Flashed the stock ROM using Mi Flash tool. It flashed OK but my MI A3 sensors are not working. Someone said Flash persist.img via TWRP but when I try to flash it asked me in which partition to flash.
Partitions available are:
bluetooth
modem
System Image
Dtbo
Vendor Image
splash
Boot
Install Recovery Ramdisk
I am confused where to flash. If this method isnt suitable as you said then guide me what to do. I have Global Fastboot ROM for Android 9 Version 3.16.0.PFQMIXM for Mi A3 available. Should I flash this using Mi Flash tool? Does it solve sensor issues or not? Please help.
Click to expand...
Click to collapse
If you are on stock android 9 now then flash an android 10 custom rom and then downgrade to android 9 like you did. Downgrading from stock 10 to stock 9 causes big issues like you are having.
If you did flash persist.IMG you would have caused stuff in your device to break forever without any way of fixing it don't do it!!

garylawwd said:
If you are on stock android 9 now then flash an android 10 custom rom and then downgrade to android 9 like you did. Downgrading from stock 10 to stock 9 causes big issues like you are having.
If you did flash persist.IMG you would have caused stuff in your device to break forever without any way of fixing it don't do it!!
Click to expand...
Click to collapse
I updated it to Stock Android 10 OTA update using TWRP Recovery and re-flashed TWRP and Magisk ZIP using TWRP and now sensors and phone is working fine. I know Android 10 for Mi A3 have some bugs but I decided to live with it until Stable Android 10 update made available by Xiaomi. Flashing Custom Android 10 ROMs have mixed reviews and have bugs so I decided to stay on Stock.
I tried flashing persist.img by mounting Persist partition using TWRP before doing this but nothing happens and sensors didn't worked. Now they are working.

garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
No problem in downgrade ,, i Already downgraded. No bugs facing!
---------- Post added at 06:34 AM ---------- Previous post was at 06:32 AM ----------
vjrx88 said:
I updated it to Stock Android 10 OTA update using TWRP Recovery and re-flashed TWRP and Magisk ZIP using TWRP and now sensors and phone is working fine. I know Android 10 for Mi A3 have some bugs but I decided to live with it until Stable Android 10 update made available by Xiaomi. Flashing Custom Android 10 ROMs have mixed reviews and have bugs so I decided to stay on Stock.
I tried flashing persist.img by mounting Persist partition using TWRP before doing this but nothing happens and sensors didn't worked. Now they are working.
Click to expand...
Click to collapse
Lol i came back to 9 ,, untill stable comes or i will use pixel rom ?

Kaissner said:
I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!
Click to expand...
Click to collapse
EDIT: Solved it by flashing this inofficial TWRP: https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
I have a problem. I am stuck on fastboot. I followed the tutorial unto step 4:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp.img
target reported max download size of 803475456 bytes
sending 'boot_a' (39892 KB)...
OKAY [ 0.910s]
writing 'boot_a'...
OKAY [ 0.197s]
finished. total time: 1.111s
But after this the phone always reboots to fastboot, I can't boot into TWRP or the system. Plz help.

spring_roll said:
EDIT: Solved it by flashing this inofficial TWRP: https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
I have a problem. I am stuck on fastboot. I followed the tutorial unto step 4:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp.img
target reported max download size of 803475456 bytes
sending 'boot_a' (39892 KB)...
OKAY [ 0.910s]
writing 'boot_a'...
OKAY [ 0.197s]
finished. total time: 1.111s
But after this the phone always reboots to fastboot, I can't boot into TWRP or the system. Plz help.
Click to expand...
Click to collapse
I know you solved it but the reason the other twrp wasn't working for you is because it is built only for Android pie and I'm assuming you have Android 10. That's why you always booted to fastboot. The installer.zip will work with any Android version but the twrp.img files are built using kernels of a specific Android version

garylawwd said:
I know you solved it but the reason the other twrp wasn't working for you is because it is built only for Android pie and I'm assuming you have Android 10. That's why you always booted to fastboot. The installer.zip will work with any Android version but the twrp.img files are built using kernels of a specific Android version
Click to expand...
Click to collapse
Ok thx for the info.
Another question. I didn't understand step 5:
"5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay)"
Where do I have to move and flash the ZIP? I just skipped this step and now I have the ROM installed which I wanted (PE Plus).
Do I have to do something now or is TWRP installed properly now? Can I fetch this step later?

spring_roll said:
Ok thx for the info.
Another question. I didn't understand step 5:
"5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay)"
Where do I have to move and flash the ZIP? I just skipped this step and now I have the ROM installed which I wanted (PE Plus).
Do I have to do something now or is TWRP installed properly now? Can I fetch this step later?
Click to expand...
Click to collapse
For you I don't think twrp is installed now. Some ROMs have twrp built in but if not then you have to manually flash twrp every time you flash a ROM or it gets overwritten with stock recovery.
When you flash the twrp.img and boot twrp it isn't actually installed, you are running it in ram and when you reboot it goes out of ram and your left with an un-bootable slot due to your boot slot being messed up from flashing the twrp.img and twrp won't stay installed.
For it to be installed properly you need to flash twrp.zip which will patch your boot.img with twrp and install it.
But as I said everytime you flash a ROM this will overwrite twrp and it will be gone unless the twrp.zip is flashed in twrp before rebooting.
Not as easy as it used to be by just installing twrp once and it is there forever. The new era of Android

Flashing failed completly, could repair it. What do i do now?

What happend:
I bought a used Mi A2 lite with stock Android 8. Because i already used LineageOS and really love it, i want to continue to use it.
I did the flashing process a few times wrong. After the help of a very kind user i did it as it was supposed to be.
mustaphakosar said:
Let me sum up the process which will probably answer your all questions.
Once you opened the bootloader and flashed TWRP image successfully and saw TWRP screen on your phone, unplug it from PC.
IF you will install a custom rom, than
1- format data, type 'yes'. Reboot to recovery
2- advaanced wipe( everyting except sd card) (ı assume you should have put custom rom file and twrp.installer.zip to your sd card)
3- install custom rom and twrp.installer.zip(choosing to upload from your sdcard, you will be able to see them)
4- go back. Press "reboot" but don't reboot anything. From reboot menu, change slot(if you're at slot 'a', change your slot to 'b', vice versa)
5- now you can press reboot to recovery.
6- once recovery(twrp) opens, you can install gapps and magisk.
7- reboot the system.
Click to expand...
Click to collapse
Doing so cause, that my Phone didn't boot the OS anymore. I could see the Android ONE bootlogo, after that the screen turned black. Phone must be still running because PC detected a device, when i connected the phone to my PC.
If i keep pressing Louder and Start i could enter recovery, with quieter i could enter fastboot.
Thankfully i discovered this thread:
never ending boot after stock ROM install
My Mi A2 Lite had stock rom v10.0.18.0, unlocked bootloader, Magisk v20.3 and TWRP using Offain v3.3.1. I wanted to try dotOS custom ROM and followed this tutorial: https://github.com/tkchn/daisyinstall I begin with step 1 installing daisy...
forum.xda-developers.com
and fixed the Phone so i can start an OS again. Now is my question, what did go wrong? What is the best way to continue from this point to flash LineageOS on my phone? Do i have to update the OS from the thread first and try it again?
Phone is still OEM unlocked.
Thank you guys in advance!

Ok i got it now. For whoever will find this in the future:
I started at the point above and updated the Stock Android 9 to the latest version.
1. Enable USB-Debugging and open Bootloader in the settings
2. Shut down Phone and start into fastboot
3. Use command: "fastbood oem unlock"
This will cause a factory reset, be aware
4. Check settings and go into fastboot again, then use command
"fastboot boot <name of your twrp image>"
Proceed this way:
GitHub - tkchn/daisyinstall: An installation guide for custom ROMs on Xiaomi Mi A2 Lite
An installation guide for custom ROMs on Xiaomi Mi A2 Lite - GitHub - tkchn/daisyinstall: An installation guide for custom ROMs on Xiaomi Mi A2 Lite
github.com
Enjoy

[GUIDE] [EMUI9] P20 Lite Basics

Spoiler: Quick Links
Official LineageOS 16.0 (15.02.2021)
.401 Stock Images (C432)
Stock Recovery
Stock E-recovery
Official TWRP (3.7.0)
Official TWRP (3.4.0-1)
Modified TWRP (3.4.0)
Heavily Modified TWRP (3.4.0)
Magisk Patched Recovery (25.2)
Magisk-Delta Patched Recovery (25.2-delta)
Stock Kernel (4.9.148)
Phenix Kernel (4.9.319 by Turex)
Phenix Permissive Kernel (4.9.319 by Iceows)
Phenix Permissive Kernel (4.9.235 by Abdelhay.ali)
Phenix Enforcing and Permissive Kernel for Android 13 (4.9.319 by Abdelhay.ali)
Selinux Rules for Android 13 (by Abdelhay.ali)
Everything Else (47GB)
Special key combos:
Power + Vol+ = Recovery Mode
While USB connected, Power + Vol+ = Erecovery Mode
While USB connected, Vol- = Fastboot
Plug USB while holding down Vol+ + Vol- = Download Mode
Power + Vol+ + Vol- = Force Dload
Flashing Any GSINote:Phh is "retiring". Community of builders created trebledroid initiative to keep his work alive. Don't expect same level of quality for a while.
Use vndklite variants.
At no point you need to wipe /data or any other partition. Just do factory reset.
If you want to backup via twrp you need to have encryption disabled.
Almost all chromium based browsers including chrome freeze after few minute of use. That is caused by DRM not working as intended in gsis. To fix it flash DRM fix.
Permissive kernel shouldn't be used daily. Please only use it for debugging purposes.
Prerequisites:
ADB and Fastboot Installed (1)
Any Arm64 AB GSI image (1) (2) (3) (4) (5)
Google apps package (Optional) (1) (2) (3) (4)
TWRP
Unlocked Bootloader
Spoiler: Android 12 and Below
Spoiler: GSI with GAPPS
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash gsi image: fastboot flash system drag & drop img file to console
Flash Stock Recovery: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into recovery: power + vol+ while NOT connected to pc
Factory reset: Factory Reset > Type yes > Press power
Boot into system
Spoiler: Vanilla GSI + Gapps + Zips
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash gsi image: fastboot flash system drag & drop img file to console
Flash Phenix Kernel (Optional): fastboot flash kernel and drag & drop img file to console
Flash this TWRP: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into recovery: power + vol+ while NOT connected to pc
Factory reset: Wipe > Swipe Factory Reset
Resize system: Wipe > Advanced Wipe > Tick System > Repair or Change File System > Swipe Resize File System
if it fails issue these commands from your computer:
adb shell "/sbin/e2fsck -fp /dev/block/platform/hi_mci.0/by-name/system"
adb shell "/sbin/resize2fs /dev/block/platform/hi_mci.0/by-name/system"
Encrypt or Decrypt /Data (Optional): Mount > Tick Vendor > adb push drag & drop fstab file to console /vendor/etc
Flash DRM fix (Optional): ''
Flash NFC fix (Optional / Might not Work): ''
Flash Gapps Zip (Optional): ''
Boot into system: Reboot > System
Spoiler: Android 13 and Beyond(?)
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash gsi image: fastboot flash system drag & drop img file to console
Flash one of these kernel (Optional): fastboot flash kernel and drag & drop img file to console
Flash this TWRP: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into recovery: power + vol+ while NOT connected to pc
Factory reset: Wipe > Swipe Factory Reset
Flash this AIO fix : Advanced > ADB Sideload > Swipe to Start Sideload > Write adb sideload and drag & drop zip file to console
Flash Gapps Zip (Optional): ''
Boot into system: Reboot > System
Spoiler: Tweaks
Spoiler: TWRP on Erecovery, Magisk on Recovery Setup
Flash over to erecovery:
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash one of these (1) (2) twrp images: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into twrp: power + vol+ while NOT connected to pc
Push twrp to /cache: adb push drag & drop img file to console /cache
Flash twrp to erecovery: Install > Install Image > Select twrp image from /cache folder > Pick erecovery_ramdisk partition > Swipe
After you set up your phone and made sure you don't need stock recovery, flash magisk:
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash magisk patched image: fastboot flash recovery_ramdisk and drag & drop img file to console
From now on this is how you boot:
No keypress: System (Long yellow warning)
Power & Vol+ before Yellow Warning : System with magisk (Short yellow warning)
Vol+ on Yellow Warning : TWRP
If you want to return to stock erecovery, do these:
Boot into twrp
Push erecovery image to /cache: adb push drag & drop img file to console /cache
Flash erecovery to erecovery: Install > Install Image > Select erecovery image from /cache folder > Pick erecovery_ramdisk partition > Swipe
Spoiler: Passing Safetynet (For Android 12 and Below
Keep in mind that Safetynet is deprecated and Google is encouraging developers to switch to Play Integrity API. To pass safetynet you need to have 3 checkmarks, as such you'll need to follow all 3 instructions I'm about to give you.
Spoiler: Evaluation Type Basic
Disable "Spoof Pixel 5" & Enable Safetynet in phh options then reboot.
Download YASNAC from play store and check for "Evaluation Type" from result.
If it says Basic and others fail you can skip this part.
If test fails or doesn't finish do these:
Install Magisk
Enable Zygisk & Enforce denylist
Install Universal SafetyNet Fix module by kdrag0n
Now check YASNAC again. It should finish test and say Basic in evaluation type.
Spoiler: Basic Integrity Fail
This happens because root is detected most of the time.
If your GSI has Dynamic Root, uncheck root from phh settings.
If your GSI has SU, securize from phh settings.
If you had to flash magisk because of evaluation type, tick google play and google play services in denylist.
If those didn't fix, contact GSI maintainer.
Spoiler: CTS Profile Match Fail
This happens because build fingerprint is not play certified.
Make sure you have safetynet option ticked in phh settings and do these:
Edit /data/adb/phh/secure
Add these 2 lines to bottom:
resetprop_phh ro.build.fingerprint HUAWEI/ANE-LX1/HWANE:9/HUAWEIANE-L01/9.1.0.368C432:user/release-keys
resetprop_phh ro.build.version.security_patch 2020-08-01
Reboot and test again.
Everytime you untick safetynet you have to edit this file again. You can also pick any other fingerprint from here should you choose to. You need both fingerprint and patch date. If you want to simulate other devices add following lines:
resetprop_phh ro.product.brand HUAWEI
resetprop_phh ro.product.device HWANE
resetprop_phh ro.product.manufacturer HUAWEI
resetprop_phh ro.product.model ANE-LX1
resetprop_phh ro.product.name ANE-LX1
Spoiler: Passing Play Integrity (For Android 13 and Beyond)
If you want to pass it you're going to have to read this wall of text. I can't shorten it.
What is Play Integrity:
Google enforces Play Inregrity once your api level is set to 33 (android 13). I currently don't have enough information about it other than apps can decide which checks to perform on your device. One of those checks is called strong integrity. We can't pass strong integrity because it requires hardware backed checks which our device lack. However you can still fool some apps that don't enforce strong integrity.
How you can fool it:
Ever since magisk retired magiskhide, some forks have been made to keep it maintained and improved. One of those forks is Magisk Delta. Before you head over to it's github and install it, you still need to install a valid CTS fingerprint. Then you can install Magisk Delta.
Steps:
Disable Spoof Pixel 5 & Enable Safetynet from phh settings if they exist.
Add these 2 lines to bottom of /data/adb/phh/secure (create if it doesnt exist) & Reboot
resetprop_phh ro.build.fingerprint HUAWEI/ANE-LX1/HWANE:9/HUAWEIANE-L01/9.1.0.368C432:user/release-keys
resetprop_phh ro.build.version.security_patch 2020-08-01
If you have magisk :
- Download Magisk Delta apk
- Change .apk to .zip
- Install it as magisk module
If you don't have magisk :
- Download & install Magisk Delta apk
- Patch recovery_ramdisk & flash it via fastboot
Enable Zygisk and MagiskHide from Magisk Delta App
Install this module : https://github.com/HuskyDG/safetynet-integrity-fix/releases
MAKE SURE GMS IS NOT IN HIDELIST
Reboot and test safetynet. (Feel free to link any app that tests for Play Integrity)
Spoiler: I went back to EMUI, why it looks like aosp?
That happens because EMUI stores it's themes and few stock apps in /data/hw_init folder. When you factory reset with stock recovery, they are preserved. But when you use twrp to factory reset they are removed. Doing factory reset once from twrp is enough to make EMUI think it's corrupted, in acuality it isn't. To fix it you can either let EMUI update from system settings or you can download this, extract hw_init folder and push folder to /data from twrp with this command :
adb push drag & drop hw_init folder to console /data
Flashing LineageOS 16.0Note:Stock kernel from EMUI .300> have trouble with wifi. Use Phenix 4.9.319 or above to fix it.
Prerequisites:
ADB and Fastboot Installed (1)
Google apps package (Pick Pie or 9.0 editions) (1) (2) (3) (4)
LineageOS Zip (From Archive or From Mega)
Phenix Kernel (Else you won't have wi-fi)
TWRP (3.4.0 is needed for factory reset functionality)
Unlocked Bootloader
Spoiler: Steps
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash this TWRP: fastboot flash recovery_ramdisk and drag & drop img file to console
Flash Phenix Kernel (Required for Wi-Fi): fastboot flash kernel and drag & drop img file to console
Boot into twrp: power + vol+ while NOT connected to pc
Flash lineage zip: Advanced > ADB Sideload > Swipe to Start Sideload > Write adb sideload and drag & drop zip file to console
Factory reset: Wipe > Swipe Factory Reset
Boot into Vanilla LineageOS or Keep following to flash gapps
Encrypt or Decrypt /Data (Optional): Mount > Tick Vendor > adb push drag & drop fstab file to console /vendor/etc
Flash gapps zip: Advanced > ADB Sideload > Swipe to Start Sideload > Write adb sideload and drag & drop zip file to console
Boot into system: Reboot > System
Getting Stock Firmware Files And DowngradingSources:
A certain russian site (linking is prohibited)
EMUI's System Updater (via root)
Firmware Finder (Revived)
HiSuite
Huawei Update Extractor
HuRUpdater Guide / HuRUpdater Download (For older builds)
HwOTA8 (For Emui 8)
Spoiler: Getting Individual Images
Firmware finder has been revived and you can use that to get your prefered cust or build.
If you need only one image not the whole build, I uploaded each one you'd typically need below.
CUST.img
DTS.img
ERECOVERY_KERNE.img
ERECOVERY_RAMDI.img
ERECOVERY_VBMET.img
ERECOVERY_VENDO.img
FASTBOOT.img
KERNEL.img
ODM.img
PRODUCT.img
RECOVERY_RAMDIS.img
RECOVERY_VBMETA.img
RECOVERY_VENDOR.img
SYSTEM.img
VBMETA.img
VENDOR.img
XLOADER.img
They are from .401 c432.
If you wiped /data once you probably won't have emui themes etc if you go back to emui. To fix that you can push hw_init folder (in data.7z) to /data. Not the contents of it, just put the folder in root of /data. It should be like this: /data/hw_init
Spoiler: Hisuite
Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip to your documents folder. update_full_base.zip file contains main UPDATE.APP. You can extract images from it with Huawei Update Extractor
Spoiler: EMUI's System Updater
Flash magisk patched image from quick links. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot because recovery is not stock. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done go to /data/update with a root file explorer. Copy HwOUC folder to internal storage and from there to your pc. There should be 3 folders with numbers. You can find our main update_full_base.zip in one of them.
Spoiler: Downgrading
Spoiler: From EMUI 9 to EMUI 9
Spoiler: Using just the SYSTEM.IMG
Get files of your prefered build. I recommend build .278. Extract SYSTEM.IMG from UPDATE.APP via huawei update extractor and flash it with fastboot flash system . Factory reset with stock recovery then flash any TWRP except for the official ones. Official TWRPs freezes when wiping /data which is what we need to do. After wiping /data boot into system. You should have aosp background with square app icons if you did correctly. Check for system updates and it should find your current build. Download and install.
Spoiler: Using dload from Certain Russian Site
BOOTLOADER WILL RELOCK, DON'T DO THIS IF YOU DON't HAVE YOUR BL CODE
For this you need to have a sd card that is formated as exfat. Fat32 doesn't allow >4gb files so exfat is required. Download your prefered build from Androidhost.ru or mega link above. Inside the zip file you'll find a folder named dload. Extract this folder to somewhere and transfer it to your sd card. Folder structure should look like below. Hw_eu and L01/L21 will depend on your region and single/dual sim status. After this unplug your phone and shut it down. Start pressing vol- vol+ and power all at the same time. Different kind of yellow warning will appear and a screen with blue progress bar over black background will appear. If you downloaded correct variant for your phone it'll start progressing. After process is done you'll boot into stock emui with NO yellow warning. This is because your bootloader is locked. Do whatever you want at this point but remember, unlocking bootloader again will low level factory reset your phone.
-/storage/AAAA-BBBB/dload
---/update_sd
---/ANE-L01_hw_eu
---/ANE-L21_hw_eu
Spoiler: From EMUI 9 to EMUI 8
If I recall correctly there is only one way to do this. You can't dload between emui versions. You also need to be on stock emui for hisuite to function. Some people say a specific hisuite version is required but it wasn't the case for me. Plug your phone to pc, hisuite should show up beside your phone in drives section. Install it and open it. Do whatever it instructs you to function correctly. After you see your phone in app click Update button. Then click on "Earlier Versions". It'll show version 8.0.0.167 along with some warnings. Rest it pretty straightforward. Follow along and it'll return you back to emui 8. But if you're doing this to unlock your bootloader, build .167 is not enough. Exploit that dc-unlocker uses is patched in this version. So you have to roll back further. I had success with .125 build but up until .150 could work. Link to .125 build.
edit ? : Revised guide

Frax3r said:
Hello there! Alive parts of this forum is still filled with simple help requests so I decided to put together a simple all-in-one thread that basically covers most stuff. I don't wanna get into bootloader unlocking because right now only free way to do so is with potatoNV which I do not know how to use. Dc-unlocker is an option too but it is 4€ so pick your poison.Special key combos:
Power + Vol+ = Recovery Mode
While USB connected, Power + Vol+ = Erecovery Mode
While USB connected, Vol- = Fastboot
Plug USB while holding down Vol+ + Vol- = Download Mode
Power + Vol+ + Vol- = Force Dload
Flashing LineageOS 16.0Prerequisites:
Emui Version below 9.1.0.300
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Los16 zip
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip
Steps:
Get the Prerequisites
I recommend sending los 16 zip, recovery_ramdis.img and gapps zip to sd card if possible
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Install and select los 16 zip file
If you want to disable encryption do it now
Press Install and press Install Image
Select and flash stock recovery_ramdis.img to recovery_ramdisk partition
Press Reboot and select shut down
Press and hold power + vol+ buttons until short yellow warning shows up
Select factory reset and type yes, while it is doing that plug the phone to pc
After factory reset is complete select reboot option and hold down vol- until you're at fastboot
Repeat step 6-7-8
Los 16 don't need to be resized so go to install and select gapps zip
Reboot to system
Flashing Any GSIPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
GSI image (1) (2)
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip (Optional)
Notes:If you're gonna use Phh's AOSP11 and anything that based on it (with the exception of @eremitein's stuff), use arm64-ab-vndklite variant. For anything else use full vndk version. Full vndk version of Phh's AOSP11 does not allow you to resize system on any twrp.
Steps for gapps versions:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
You're good to boot up the system
Steps for vanilla versions with custom gapps:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
If you want to disable encryption do it now
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
Plug your phone back and press reboot from screen
While booting press and hold vol- button until you're at fastboot
Write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Wipe, press Advanced Wipe, select System, press Repair or Change File System, press Resize File System, swipe to resize
Press Install, select and flash gapps zip
Reboot to system
Disable EncryptionPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Official TWRP
Stock recovery_ramdis.img
Notes:You can disable encryption at any step, even after booting, but in order to disable it you have to do a factory reset from stock recovery_ramdis. Because of this I recommend doing between flashing gsi and flashing gapps.
Steps:
Get the Prerequisites
Boot to TWRP (power + vol+ after shutting down)
Allow modifications
Press Mount, select Vendor
Connect phone to PC
You can do next part 2 ways, if you're good with command line interface use steps 7 through 11, if not skip to step 12
Type adb shell and press enter
Type nano /vendor/etc/fstab.hi6250 and press enter
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Press Ctrl + X then Y and press enter
Go to step 18
Type adb pull /vendor/etc/fstab.hi6250 and press enter
If you have adb in your $PATH go to your user profile folder, if not go to folder where adb.exe resides
Open fstab.hi6250 via a text editor (please use notepad++)
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Save file and open a command prompt
Send this command adb push ./fstab.hi6250 /vendor/etc/fstab.hi6250
View attachment 5422531
Now you need to do a factory reset with stock recovery_ramdis.img, if you have it installed go to step 21 if not do 19 or 20 first
If you have TWRP installed, press Install and press Install Image then select and flash stock recovery_ramdis.img to recovery_ramdisk partition
If not shut down phone, connect it to pc and hold down vol- until you're at fastboot, then write this command fastboot flash recovery_ramdisk and drag recovery_ramdis.img over to console then press enter
Shut down phone and unplug it from pc
Press and hold power+ vol+ until you see short yellow warning
Press Factory Reset and type yes
You've successfully decrypted your phone and you're good to boot up or flash gapps
Getting Stock Firmware Files And DowngradingPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Huawei Update Extractor
Firmware Zip (EMUI8 and EMUI9)
HiSuite
Erecovery
EMUI's System Updater (via root)
HuRUpdater Guide / HuRUpdater Download
HwOTA
Getting stock files are problematic because of huawei. Least shadiest way to get them are the hardest so bear with me.
Androidhost.ru : Click the EMUI9 from prerequisites and search p20 lite. You should get a wide variety of versions to pick from. Make sure to match the Cust in the file to yours if you don't know what you're doing. C432 for Europe for example. After you download the zip file open it up and find the dload folder. You can either get this folder and paste it right into your sd card to force dload or you can open this folder and extract update_sd.zip. Inside update_sd.zip you'll find a file named UPDATE.APP. Use Huawei Update Extractor to open this file and there you'll see all the partitions you need. If HUE gives error while opening it, go to settings and untick "Verify file checksum". You can extract .img files by right clicking and selecting extract option on each partition. Normally you can't open these .img files but after pushing them through simg2img you'll be able to explore them too. But lets be real if you need guides for this, all you need is recovery_ramdis.img.
Using Dload Folder : Your sd card can't be FAT32 for this. FAT32 by nature don't allow files larger than 4gb so you can't get this folder to your sd card. Format it to ExFat via any guide on the internet then copy the dload folder to your sd card's root. It can't be inside any folders. Then shut your phone and press Power + Vol+ + Vol- all at the same time. It'll boot to erecovery which'll check the integrity of files then install them regardless of your EMUI version. So it is a good way to downgrade. Keep in mind tho you can't dload back to emui 8 from emui 9. And any successful dload will lock your bootloader back.
Hisuite : You can actually get firmware files pretty easily with hisuite but it requires real work. You see, hisuite downloads firmware files right into your documents folder. Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip. It might not get all 3 files most of the time so you have to copy each of them and update a few versions consecutively to get them. Keep in mind, it deletes each update file after it is successful so make sure to make a copy of them some place else. I recommend reverting back to EMUI8 through hisuite and then updating it to latest one to get all files. It is tidious but you need to do this once. It doesnt update you to .370 from .132. It'll send you .132 then .200 then .368 then latest whatever. You can actually use these files with HuRu updater or HwOTA to manually update. Or you can get the UPDATE.APP inside them and extract images with Huawei Update Extractor.
Erecovery : This one requires some network knowledge and it'll only get you the latest version so I don't think it worth the hassle. You need a router that allows you to change dns address for DHCP clients. Which most of them do these days. Now you need to create and run a dns server on your pc. I recommend adguard home. Pihole works too. Use Windows Subsystem For Linux or Docker to install either of them. Once you get them up and working set them to log dns requests. I believe you know where this is going. Open your router's interface and enter adguard home/pihole ip address which maps back to your pc's local address. Check if it works or not by opening up few sites on your phone which should be connected to your wifi and isn't set up to use a different dns server. If all is good open up erecovery on your phone and connect to your wifi. If you set it up correctly it should get the latest version from huawei which will show up on your log. Use that url to download it to your pc and extract it same as others. There was a paid service that used this method to send specific versions to your erecovery.
EMUI's System Updater : This is tricky and my favorite. Get the official TWRP .img and patch it with magisk manager. Then flash it via fastboot. I know, "twrp and magisk? wtf?" just do it. It takes a long time to boot but it works don't question me right now. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot cuz recovery is hijacked. duh. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done search for a folder named HwOUC in /system. Copy it to internal storage and from there to your pc. You can find our main UPDATE.APP inside update_full_base.zip. Other zips include cust and all that which HuRu and HwOTA requires.
MagiskPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Stock recovery_ramdis.img
Notes:Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Steps to install older version:
Get the Prerequisites
No, I mean literally just get the Prerequisites and thats it
Open up your browser and find a bin service (pastebin will suffice)
Create a paste with following
Code:
{
"app": {
"version": "8.0.7",
"versionCode": "4834",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk",
"note": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app/src/main/res/raw/changelog.md"
},
"stub": {
"versionCode": "18",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/stub-release.apk"
},
"uninstaller": {
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip"
},
"magisk": {
"version": "v21.4",
"versionCode": "21400",
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip",
"note": "https://topjohnwu.github.io/Magisk/releases/21400.md",
"md5": "ee6dd05579776e7de3a6077087846e53"
}
}
Get the paste's raw url
Take the recovery_ramdis.img to internal storage
Install magisk manager 8.0.7
Open it's settings and select custom channel
Write the raw url you just created
Allow it to check for updates and it'll find that 21.4 is the latest version
Click install and select recovery_ramdis.img
After it finishes patching get the magisk_patched.img to your pc
Get your phone to fastboot mode
After connecting to pc, write this fastboot flash recovery_ramdisk to console and drag magisk_patched.img over to console and press enter
Now if you enter recovery it'll boot to android with magisk but if you boot normally it will not detect magisk so each time you restart you have to use Power + Vol+ combo in order to get magisk
Remember to switch custom channel to stable channel if you want to receive updates.
I know that you can pretty much reduce the amount of flashing and restarting by flashing twrp to erecovery but since erecovery is a lifeline for most people here I decided not to get into that. But for those who are interested check this thread.
Edit: Grammar
Click to expand...
Click to collapse
I wish good luck to those who will use your guide .

Among other things, the HwOTA and HuRupdater methods have not worked since February (unless someone has the necessary files stored on the disk). Huawei changed servers and Firmware Finder is dead.
EMUI 8 firmware download doesn't work for the same reasons .

avenger.forsyth said:
I wish good luck to those who will use your guide .
Click to expand...
Click to collapse
Everyone has the right to write a guide, but the author must know what he is writing about. Guide made by the "copy/paste" method will not help anyone very much...

Frax3r said:
Hello there! Alive parts of this forum is still filled with simple help requests so I decided to put together a simple all-in-one thread that basically covers most stuff. I don't wanna get into bootloader unlocking because right now only free way to do so is with potatoNV which I do not know how to use. Dc-unlocker is an option too but it is 4€ so pick your poison.Special key combos:
Power + Vol+ = Recovery Mode
While USB connected, Power + Vol+ = Erecovery Mode
While USB connected, Vol- = Fastboot
Plug USB while holding down Vol+ + Vol- = Download Mode
Power + Vol+ + Vol- = Force Dload
Flashing LineageOS 16.0Prerequisites:
Emui Version below 9.1.0.300
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Los16 zip
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip
Steps:
Get the Prerequisites
I recommend sending los 16 zip, recovery_ramdis.img and gapps zip to sd card if possible
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Install and select los 16 zip file
If you want to disable encryption do it now
Press Install and press Install Image
Select and flash stock recovery_ramdis.img to recovery_ramdisk partition
Press Reboot and select shut down
Press and hold power + vol+ buttons until short yellow warning shows up
Select factory reset and type yes, while it is doing that plug the phone to pc
After factory reset is complete select reboot option and hold down vol- until you're at fastboot
Repeat step 6-7-8
Los 16 don't need to be resized so go to install and select gapps zip
Reboot to system
Flashing Any GSIPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
GSI image (1) (2)
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip (Optional)
Notes:If you're gonna use Phh's AOSP11 and anything that based on it (with the exception of @eremitein's stuff), use arm64-ab-vndklite variant. For anything else use full vndk version. Full vndk version of Phh's AOSP11 does not allow you to resize system on any twrp.
Steps for gapps versions:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
You're good to boot up the system
Steps for vanilla versions with custom gapps:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
If you want to disable encryption do it now
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
Plug your phone back and press reboot from screen
While booting press and hold vol- button until you're at fastboot
Write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Wipe, press Advanced Wipe, select System, press Repair or Change File System, press Resize File System, swipe to resize
Press Install, select and flash gapps zip
Reboot to system
Disable EncryptionPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Official TWRP
Stock recovery_ramdis.img
Notes:You can disable encryption at any step, even after booting, but in order to disable it you have to do a factory reset from stock recovery_ramdis. Because of this I recommend doing between flashing gsi and flashing gapps.
Steps:
Get the Prerequisites
Boot to TWRP (power + vol+ after shutting down)
Allow modifications
Press Mount, select Vendor
Connect phone to PC
You can do next part 2 ways, if you're good with command line interface use steps 7 through 11, if not skip to step 12
Type adb shell and press enter
Type nano /vendor/etc/fstab.hi6250 and press enter
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Press Ctrl + X then Y and press enter
Go to step 18
Type adb pull /vendor/etc/fstab.hi6250 and press enter
If you have adb in your $PATH go to your user profile folder, if not go to folder where adb.exe resides
Open fstab.hi6250 via a text editor (please use notepad++)
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Save file and open a command prompt
Send this command adb push ./fstab.hi6250 /vendor/etc/fstab.hi6250
View attachment 5422531
Now you need to do a factory reset with stock recovery_ramdis.img, if you have it installed go to step 21 if not do 19 or 20 first
If you have recovery_ramdis.img in your sd card, press Install and press Install Image then select and flash stock recovery_ramdis.img to recovery_ramdisk partition
If not shut down phone, connect it to pc and hold down vol- until you're at fastboot, then write this command fastboot flash recovery_ramdisk and drag recovery_ramdis.img over to console then press enter
Shut down phone and unplug it from pc
Press and hold power+ vol+ until you see short yellow warning
Press Factory Reset and type yes
You've successfully decrypted your phone and you're good to boot up or flash gapps
Getting Stock Firmware Files And DowngradingPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Huawei Update Extractor
Firmware Zips
HiSuite
Erecovery
EMUI's System Updater (via root)
HuRUpdater Guide / HuRUpdater Download (don't work anymore)
HwOTA (don't work anymore)
Getting stock files are problematic because of huawei. Least shadiest way to get them are the hardest so bear with me.
Androidhost.ru : Click the "Firmware Zips" from prerequisites and search p20 lite. You should get a wide variety of versions to pick from. Make sure to match the Cust in the file to yours. C432 for Europe for example. After you download the zip file open it up and find a folder named "dload". You can either get this folder and paste it right into your sd card to force dload or you can open this folder and extract update_sd.zip. Inside update_sd.zip you'll find a file named UPDATE.APP. Use Huawei Update Extractor to open this file and there you'll see all the partitions you need. If HUE gives error while opening it, go to settings and untick "Verify file checksum". You can extract .img files by right clicking and selecting extract option on each partition. Normally you can't open these .img files but after pushing them through simg2img you'll be able to explore them too. But lets be real if you need guides for this, all you need is recovery_ramdis.img.
Using Dload Folder : Your sd card can't be FAT32 for this. FAT32 by nature don't allow files larger than 4gb so you can't get this folder to your sd card. Format it to ExFat via any guide on the internet then copy the dload folder to your sd card's root. It can't be inside any folders. Then shut your phone and press Power + Vol+ + Vol- all at the same time. It'll boot to erecovery which'll check the integrity of files then install them regardless of your EMUI version. So it is a good way to downgrade. Keep in mind tho you can't dload back to emui 8 from emui 9. And any successful dload will lock your bootloader back.
Hisuite : You can actually get firmware files pretty easily with hisuite but it requires real work. You see, hisuite downloads firmware files right into your documents folder. Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip. You only need update_full_base.zip file, others are used to work on HuRUpdater and HwOTA but they are deprecated since February. Inside update_full_base.zip you'll find UPDATE.APP which you can extract images from with Huawei Update Extractor.
Erecovery : This one requires some network knowledge and it'll only get you the latest version so I don't think it worth the hassle. You need a router that allows you to change dns address for DHCP clients. Which most of them do these days. Now you need to create and run a dns server on your pc. I recommend adguard home. Pihole works too. Use Windows Subsystem For Linux or Docker to install either of them. Once you get them up and working set them to log dns requests. I believe you know where this is going. Open your router's interface and enter adguard home/pihole ip address which maps back to your pc's local address. Check if it works or not by opening up few sites on your phone which should be connected to your wifi and isn't set up to use a different dns server. If all is good open up erecovery on your phone and connect to your wifi. If you set it up correctly it should get the latest version from huawei which will show up on your log. Use that url to download it to your pc and extract it same as others. There was a paid service that used this method to send specific versions to your erecovery.
EMUI's System Updater : This is tricky and my favorite. Get the official TWRP .img and patch it with magisk manager. Then flash it via fastboot. I know, "twrp and magisk? wtf?" just do it. It takes a long time to boot but it works don't question me right now. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot cuz recovery is hijacked. duh. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done search for a folder named HwOUC in /system. Copy it to internal storage and from there to your pc. You can find our main UPDATE.APP inside update_full_base.zip. Other zips include cust and all that which HuRu and HwOTA used to require.
MagiskPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Stock recovery_ramdis.img
Notes:Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Steps to install older version:
Get the Prerequisites
No, I mean literally just get the Prerequisites and thats it
Open up your browser and find a bin service (pastebin will suffice)
Create a paste with following
Code:
{
"app": {
"version": "8.0.7",
"versionCode": "4834",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk",
"note": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app/src/main/res/raw/changelog.md"
},
"stub": {
"versionCode": "18",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/stub-release.apk"
},
"uninstaller": {
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip"
},
"magisk": {
"version": "v21.4",
"versionCode": "21400",
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip",
"note": "https://topjohnwu.github.io/Magisk/releases/21400.md",
"md5": "ee6dd05579776e7de3a6077087846e53"
}
}
Get the paste's raw url
Take the recovery_ramdis.img to internal storage
Install magisk manager 8.0.7
Open it's settings and select custom channel
Write the raw url you just created
Allow it to check for updates and it'll find that 21.4 is the latest version
Click install and select recovery_ramdis.img
After it finishes patching get the magisk_patched.img to your pc
Get your phone to fastboot mode
After connecting to pc, write this fastboot flash recovery_ramdisk to console and drag magisk_patched.img over to console and press enter
Now if you enter recovery it'll boot to android with magisk but if you boot normally it will not detect magisk so each time you restart you have to use Power + Vol+ combo in order to get magisk
Remember to switch custom channel to stable channel if you want to receive updates.
I know that you can pretty much reduce the amount of flashing and restarting by flashing twrp to erecovery but since erecovery is a lifeline for most people here I decided not to get into that. But for those who are interested check this thread.
Edit: Grammar
Edit 2: Update about HwOTA and HuRUpdate
Click to expand...
Click to collapse
Oh, man! Are you serious?

I don't know what anyone expects from a guide... Is it better to just repeat the same thing over and over again? "Flash system with fastboot, factory reset with stock recovery, flash and boot twrp, resize system, flash gapps" is literally the summary of this. That summary is what you'll get as an answer if you ask for help on any telegram group. Instead of saying flash twrp, I wrote how you can flash twrp. Thats why it's so long. This guide is for "how" not "what".

Frax3r said:
I don't know what anyone expects from a guide... Is it better to just repeat the same thing over and over again? "Flash system with fastboot, factory reset with stock recovery, flash and boot twrp, resize system, flash gapps" is literally the summary of this. That summary is what you'll get as an answer if you ask for help on any telegram group. Instead of saying flash twrp, I wrote how you can flash twrp. Thats why it's so long. This guide is for "how" not "what".
Click to expand...
Click to collapse
I would say that even so far, people have managed to install GSI, Magisk, etc. .
Btw, Recovery and eRecovery are the same for all models and build numbers . They are even compatible with LLD and BND models.

Frax3r said:
Thats why it's so long
Click to expand...
Click to collapse
It is long because because of procedures that are too complicated, e.g. chapter "Disable Encryption" .
It is long because of duplicate procedures, e.g. chapter "Flashing Any GSI".
Sorry but Chapter "Magisk" is useless. Nowadays nobody needs to install the old Magisk. Rather focus on some of the nuances of installing Magisk on EMUI 9.1 that would be helpful.
Frax3r said:
Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses.
Click to expand...
Click to collapse
No comment...
Frax3r said:
Get the official TWRP .img and patch it with magisk manager
Click to expand...
Click to collapse
No comment...
Have a good day!

Frax3r said:
Hello there! Alive parts of this forum is still filled with simple help requests so I decided to put together a simple all-in-one thread that basically covers most stuff. I don't wanna get into bootloader unlocking because right now only free way to do so is with potatoNV which I do not know how to use. Dc-unlocker is an option too but it is 4€ so pick your poison.
I have uploaded all my resources for this device to here. Inside EMUI folder you'll find some of the versions that I archived with the methods I explained on getting firmwares section. You can find recovery_ramdis.img from each of these version inside RECOVERY_RAMDISK folder as well.Special key combos:
Power + Vol+ = Recovery Mode
While USB connected, Power + Vol+ = Erecovery Mode
While USB connected, Vol- = Fastboot
Plug USB while holding down Vol+ + Vol- = Download Mode
Power + Vol+ + Vol- = Force Dload
Flashing LineageOS 16.0Prerequisites:
Emui Version below 9.1.0.300
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Los16 zip
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip
Steps:
Get the Prerequisites
I recommend sending los 16 zip, recovery_ramdis.img and gapps zip to sd card if possible
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send this command from pc : adb reboot bootloader
When you're at fastboot write fastboot flash recovery_ramdisk to console and drag & drop twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Install and select los 16 zip file
If you want to disable encryption do it now
Press Install and press Install Image
Select and flash stock recovery_ramdis.img to recovery_ramdisk partition
Press Reboot and select Recovery
Press Factory Reset and type yes, while it is doing that plug the phone to pc
Press Reboot and when screen is off start holding down vol- until you're at fastboot
Repeat step 6-7-8
Los 16 don't need to be resized so press Install and select gapps zip
Press Reboot System
Flashing Any GSIPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
GSI image (1) (2)
Official TWRP
Stock recovery_ramdis.img in recovery_ramdisk partition
Your choice of gapps zip (Optional)
Notes:If you're gonna use Phh's AOSP11 and anything that based on it (with the exception of @eremitein's stuff), use arm64-ab-vndklite variant. For anything else use full vndk version. Full vndk version of Phh's AOSP11 does not allow you to resize system on any twrp.
Steps for gapps versions:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send this command from pc : adb reboot bootloader
When you're at fastboot write fastboot flash system to console and drag & drop gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Press Factory Reset and type yes
When it is done press Reboot
Steps for vanilla versions with custom gapps:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send this command from pc : adb reboot bootloader
When you're at fastboot write fastboot flash system to console and drag & drop gsi .img over to console and press enter
If you want to disable encryption do it now
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Press Factory Reset and type yes, while it is doing that plug the phone to pc
Press Reboot and when screen is off start holding down vol- until you're at fastboot
Write fastboot flash recovery_ramdisk to console and drag & drop twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Wipe, press Advanced Wipe, select System, press Repair or Change File System, press Resize File System, swipe to resize then go back to main screen
Press Install, select and flash gapps zip
Press Reboot System
Disable EncryptionPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Official TWRP
Stock recovery_ramdis.img
Notes:You can disable encryption at any step, even after booting, but in order to disable it you have to do a factory reset from stock recovery_ramdis. Because of this I recommend doing between flashing gsi and flashing gapps.
Steps:
Get the Prerequisites
Flash and boot TWRP
Allow modifications
Press Mount, select Vendor
Connect phone to PC
You can do next part 2 ways, if you're good with command line interface use steps 7 through 11, if not skip to step 12
Type adb shell and press enter
Type nano /vendor/etc/fstab.hi6250 and press enter
Remove fileencryption=aes-256-xts:aes-256-cts from 16th line, make sure there's only one comma between check and reservedsize
Press Ctrl + X then Y and press enter
Go to step 18
Type adb pull /vendor/etc/fstab.hi6250 and press enter
If you have adb in your $PATH go to your user profile folder, if not go to folder where adb.exe is
Open fstab.hi6250 via a text editor (please use notepad++)
Remove fileencryption=aes-256-xts:aes-256-cts from 16th line, make sure there's only one comma between check and reservedsize
Save file and open a command prompt
Send this command adb push ./fstab.hi6250 /vendor/etc/fstab.hi6250
View attachment 5422531
Now you need to do a factory reset with stock recovery_ramdis.img
If you have recovery_ramdis.img in your sd card, press Install and press Install Image then select recovery_ramdis.img and pick recovery_ramdisk partition
If you don't have recovery_ramdis.img in your sd card, shut down phone, connect it to pc and hold down vol- until you're at fastboot, then write this command fastboot flash recovery_ramdisk and drag recovery_ramdis.img over to console then press enter
Shut down your phone and unplug it from pc
Press and hold power+ vol+ until you see short yellow warning
Press Factory Reset and type yes
You've successfully decrypted your phone and you're good to boot up or flash gapps
Getting Stock Firmware Files And DowngradingPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Huawei Update Extractor
Firmware Zips
HiSuite
Erecovery
EMUI's System Updater (via root)
HuRUpdater Guide / HuRUpdater Download (don't work anymore)
HwOTA (don't work anymore)
Getting stock files are problematic because of huawei. Least shadiest way to get them are the hardest so bear with me.
Androidhost.ru : Click the "Firmware Zips" from prerequisites and search p20 lite. You should get a wide variety of versions to pick from. Make sure to match the Cust in the file to yours. C432 for Europe for example. After you download the zip file open it up and find a folder named "dload". You can either get this folder and paste it right into your sd card to force dload or you can open this folder and extract update_sd.zip. Inside update_sd.zip you'll find a file named UPDATE.APP. Use Huawei Update Extractor to open this file and there you'll see all the partitions you need. If HUE gives error while opening it, go to settings and untick "Verify file checksum". You can extract .img files by right clicking and selecting extract option on each partition. Normally you can't open these .img files but after pushing them through simg2img you'll be able to explore them too. But lets be real if you need guides for this, all you need is recovery_ramdis.img.
Using Dload Folder : Your sd card can't be FAT32 for this. FAT32 by nature don't allow files larger than 4gb so you can't get this folder to your sd card. Format it to ExFat via any guide on the internet then copy the dload folder to your sd card's root. It can't be inside any folders. Then shut your phone and press Power + Vol+ + Vol- all at the same time. It'll boot to erecovery which'll check the integrity of files then install them regardless of your EMUI version. So it is a good way to downgrade. Keep in mind tho you can't dload back to emui 8 from emui 9. And any successful dload will lock your bootloader back.
Hisuite : You can actually get firmware files pretty easily with hisuite but it requires real work. You see, hisuite downloads firmware files right into your documents folder. Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip. You only need update_full_base.zip file, others are used to work on HuRUpdater and HwOTA but they are deprecated since February. Inside update_full_base.zip you'll find UPDATE.APP which you can extract images from with Huawei Update Extractor.
Erecovery : This one requires some network knowledge and it'll only get you the latest version so I don't think it worth the hassle. You need a router that allows you to change dns address for DHCP clients. Which most of them do these days. Now you need to create and run a dns server on your pc. I recommend adguard home. Pihole works too. Use Windows Subsystem For Linux or Docker to install either of them. Once you get them up and working set them to log dns requests. I believe you know where this is going. Open your router's interface and enter adguard home/pihole ip address which maps back to your pc's local address. Check if it works or not by opening up few sites on your phone which should be connected to your wifi and isn't set up to use a different dns server. If all is good open up erecovery on your phone and connect to your wifi. If you set it up correctly it should get the latest version from huawei which will show up on your log. Use that url to download it to your pc and extract it same as others. There was a paid service that used this method to send specific versions to your erecovery.
EMUI's System Updater : This is tricky and my favorite. Get the official TWRP .img and patch it with magisk manager. Then flash it via fastboot. I know, "twrp and magisk? wtf?" just do it. It takes a long time to boot but it works don't question me right now. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot cuz recovery is hijacked. duh. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done search for a folder named HwOUC in /system. Copy it to internal storage and from there to your pc. You can find our main UPDATE.APP inside update_full_base.zip. Other zips include cust and all that which HuRu and HwOTA used to require.
MagiskPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Stock recovery_ramdis.img
Notes:Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. New installer for magisk kinda broken for our device, because of that I recommend installing and booting an older version. It's safe to update it afterwards from magisk manager. As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Steps to install older version:
Get the Prerequisites
No, I mean literally just get the Prerequisites and thats it
Open up your browser and find a bin service (pastebin will suffice)
Create a paste with following
Code:
{
"app": {
"version": "8.0.7",
"versionCode": "4834",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk",
"note": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app/src/main/res/raw/changelog.md"
},
"stub": {
"versionCode": "18",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/stub-release.apk"
},
"uninstaller": {
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip"
},
"magisk": {
"version": "v21.4",
"versionCode": "21400",
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip",
"note": "https://topjohnwu.github.io/Magisk/releases/21400.md",
"md5": "ee6dd05579776e7de3a6077087846e53"
}
}
Get the paste's raw url
Take the recovery_ramdis.img to internal storage
Install magisk manager 8.0.7
Open it's settings and select custom channel
Write the raw url you just created
Allow it to check for updates and it'll find that 21.4 is the latest version
Click install and select recovery_ramdis.img
After it finishes patching get the magisk_patched.img to your pc
Get your phone to fastboot mode
After connecting to pc, write this fastboot flash recovery_ramdisk to console and drag magisk_patched.img over to console and press enter
Now if you enter recovery it'll boot to android with magisk but if you boot normally it will not detect magisk so each time you restart you have to use Power + Vol+ combo in order to get magisk
Remember to switch custom channel to stable channel if you want to receive updates.
I know that you can pretty much reduce the amount of flashing and restarting by flashing twrp to erecovery but since erecovery is a lifeline for most people here I decided not to get into that. But for those who are interested check this thread.
Edit: Grammar
Edit 2: Update about HwOTA and HuRUpdate
Edit 3: Simplify some steps and add my own mega.nz archive
Click to expand...
Click to collapse
Only now I have time to read your instructions carefully, what is this nonsense ???
Frax3r said:
Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. New installer for magisk kinda broken for our device, because of that I recommend installing and booting an older version.
Click to expand...
Click to collapse
I'll give you some advice if I may - don't write about things you don't understand! And this applies not only to Magisk.

avenger.forsyth said:
It is long because because of procedures that are too complicated, e.g. chapter "Disable Encryption" .
Click to expand...
Click to collapse
Is it better to just link decryption zip or write what that decryption zip does?
avenger.forsyth said:
It is long because of duplicate procedures, e.g. chapter "Flashing Any GSI".
Click to expand...
Click to collapse
People use gapps versions because they don't want to waste time by flashing zips. That's why it's 2 part. Gapps one is shorter.
Frax3r said:
Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses.
Click to expand...
Click to collapse
Magisk-in-recovery as in "magisk hijacking recovery" not "installing magisk using recovery". You can't even find huawei section in it's installation instructions. Look here and here. As for the nuance you asked, installing magisk in EMUI is literally same as installing it in GSI or LOS. You patch the image, flash the image, boot the image.
Frax3r said:
As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Click to expand...
Click to collapse
I added "ask me how I know" part for a reason. I tried. You CAN patch official twrp with magisk and it WILL boot. If a person unlocks their bootloader for the first time how is he supposed to get stock recovery_ramdis.img? Get the mmcblock of recovery_ramdisk? How is he supposed to do that if he flashes twrp over to recovery_ramdisk partition? We can't use "fastboot boot" so that's out of option. Use a different recovery_ramdis.img you might say. I TRIED. .380's recovery_ramdis.img patched with latest magisk won't boot if you're at .278. I created a folder where I patched .380 recovery with each different version of magisk starting from 20.4 up to latest version and none of them booted on los 16 which was installed upon .278. It is not universal as you might think.
-Alf- said:
Only now I have time to read your instructions carefully, what is this nonsense ???
I'll give you some advice if I may - don't write about things you don't understand! And this applies not only to Magisk.
Click to expand...
Click to collapse
Care to elaborate? I am open to constructive criticism. As for what I know, I do know that you won't find yourself bootlooping if you follow these steps by the letter. I saw your instructions on los 16 and other threads too. Here's a criticism for you, do not tell people to wipe /data or factory reset with twrps and especially do not expect them to flash twrp over to erecovery. Wiping /data or factory reset from twrp always resulted in phone freezing for me. I guess twrp in erecovery could fix freezing but there's a reason why they are asking for help and you expect them to overwrite their only lifeline. 1-2 extra rebooting and flashing won't hurt anyone. When you wipe /data or factory reset with most twrps, including official one, some folders that needs to be untouched (huawei am i right) gets deleted. So you have to use stock recovery_ramdis.img or an advanced twrp which compansates it. Check the tishserg's twrp for example. I use that not the official twrp for these things. And it can write to erecovery which is exactly why I didn't advocate on using it in this guide. Have a good day...

Frax3r said:
Here's a criticism for you, do not tell people to wipe /data or factory reset with twrps and especially do not expect them to flash twrp over to erecovery. Wiping /data or factory reset from twrp always resulted in phone freezing for me.
Click to expand...
Click to collapse
Use recommended TWRP, not 3.4.0. and above, which is not fully compatible with hi6250 devices (including official one). Did you know?
Btw, I never advised anyone to do a factory reset in TWRP, on the contrary
https://forum.xda-developers.com/t/...twrp-3-2-1-0-12-05-2018.3789306/post-85472227
Frax3r said:
New installer for magisk kinda broken for our device, because of that I recommend installing and booting an older version.
Click to expand...
Click to collapse
Everyone knows that it is possible to install the latest version right away...

-Alf- said:
Use recommended TWRP, not 3.4.0. and above, which is not fully compatible with hi6250 devices (including official one). Did you know?
Btw, I never advised anyone to do a factory reset in TWRP, on the contrary
https://forum.xda-developers.com/t/...twrp-3-2-1-0-12-05-2018.3789306/post-85472227
Everyone knows that it is possible to install the latest version right away...
Click to expand...
Click to collapse
Yes you said that here. However my own experience says otherwise. Before my current los 16 installation I used official 3.5.2. Flashed los, flashed stock recovery, flashed phenix kernel, flashed gapps all from it. I even used nano from adb shell to edit fstab.hi6250. I used backup and restore only on kernel partition but it was successful anyway. What that incompatibility be? Is it boot override thing? If you have twrp in recovery and send reboot to recovery from android it just keeps booting to twrp in each reboot even tho you select otherwise from twrp's reboot menu. BTW tishserg's twrp have an option to remove that override if you find yourself in that loop. As for factory reset part, you said format /data here. We had a discussion here because of that. My bad on reading wrong. While writing this I realised incompatibility is probably about formating /data on twrp 3.4.0 and above. If that is the case I'll update the post. Good thing I didn't tell people to format /data from twrp. My steps might be long but they are correct. It is wrong to call all this a nonsense.
Everyone might know it is possible to install latest magisk but not everyone knows how to install an older version now that magisk's future is uncertain. After magisk removes magiskhide from its code people are gonna wanna go back to latest version that worked while waiting for module version of it. Patching twrp image with magisk is highlight of this post but it is literally what flashing magisk.zip (.apk to .zip) from twrp does with the latest version. If patching twrp is bad then why is my guide to installing an older version, which allows you to select which image to patch, is the target? + With that .json, you can make magisk manager patch the image with your own modified version of magisk should you upload it somewhere and change the links.

Hi,
I'm building trying to port Ubuntu Touch to this device and I'm running into a few challenges. I have already reverted to stock 2 times and re-unlocked the bootloader (starting from EMUI 9). So far I have only flashed recovery_ramdisk with twrp as I was worried I might not be able to revert to stock if I flashed erecovery.
Question 1: Is this correct or a misunderstanding?
Installing Ubuntu Touch requires the data partition to be formatted to ext4. I can do that from twrp, but someone (maybe you) wrote that wiping the data partition with twrp was liable to create trouble.
Q2: Same question as above.
I understand Huawei requires the kernel and ramdisk to reside in separate images on separate partitions. So I have used this guide (https://wiki.postmarketos.org/wiki/Huawei_P10_Lite_(huawei-warsaw)) to separate the boot.img produced in my build, and then flashed these two image files to the kernel and recovery_ramdisk partitions respectively. However, examining the LOS 16.0 rom that can be installed, I see that it contains a "boot.img".
Q3: Can I flash my boot.img without separating into kernel and ramdisk first, and if so, which partition should I flash?
Q4: After flashing the image files I built (kernel.img and ramdisk.img along with system.img), do I need to reboot to a recovery (if so, which?) and wipe something (if so, what?) before rebooting?

aribk said:
Hi,
Question 1: Is this correct or a misunderstanding?
Q2: Same question as above.
Q3: Can I flash my boot.img without separating into kernel and ramdisk first, and if so, which partition should I flash?
Q4: After flashing the image files I built (kernel.img and ramdisk.img along with system.img), do I need to reboot to a recovery (if so, which?) and wipe something (if so, what?) before rebooting?
Click to expand...
Click to collapse
Hello,
If I understood you correctly you're asking if you can flash stock erecovery after you've modified it. Answer is yes, you can flash twrp on it and when you're done you can flash stock erecovery image over it. Fastboot won't allow you to flash anything on erecovery partition tho. So you need to use certain twrps that are capable of flashing over erecovery. s_mak and tishserg twrps should allow that iirc. First flash any one of those twrps to recovery_ramdisk then boot into it afterwards flash same twrp image to erecovery partition from inside the twrp.
Yes, if you look at last few replies in this thread that was exactly the conversation. However that is only the case with official twrp. If you use s_mak or tishserg's twrps from the mega link in the thread you should be able to wipe without a problem.
Last 2 questions are beyond me I'm afraid. PostparketOS and Ubuntu Touch are inherently very different to android and they could require some stuff that are unique to them. However I would imagine you wouldn't need to wipe anything after flashing those images.

aribk said:
Hi,
I'm building trying to port Ubuntu Touch to this device and I'm running into a few challenges. I have already reverted to stock 2 times and re-unlocked the bootloader (starting from EMUI 9). So far I have only flashed recovery_ramdisk with twrp as I was worried I might not be able to revert to stock if I flashed erecovery.
Question 1: Is this correct or a misunderstanding?
Installing Ubuntu Touch requires the data partition to be formatted to ext4. I can do that from twrp, but someone (maybe you) wrote that wiping the data partition with twrp was liable to create trouble.
Q2: Same question as above.
I understand Huawei requires the kernel and ramdisk to reside in separate images on separate partitions. So I have used this guide (https://wiki.postmarketos.org/wiki/Huawei_P10_Lite_(huawei-warsaw)) to separate the boot.img produced in my build, and then flashed these two image files to the kernel and recovery_ramdisk partitions respectively. However, examining the LOS 16.0 rom that can be installed, I see that it contains a "boot.img".
Q3: Can I flash my boot.img without separating into kernel and ramdisk first, and if so, which partition should I flash?
Q4: After flashing the image files I built (kernel.img and ramdisk.img along with system.img), do I need to reboot to a recovery (if so, which?) and wipe something (if so, what?) before rebooting?
Click to expand...
Click to collapse
aribk said:
So far I have only flashed recovery_ramdisk with twrp as I was worried I might not be able to revert to stock if I flashed erecovery.
Question 1: Is this correct or a misunderstanding?
Click to expand...
Click to collapse
Misunderstanding. You can revert to stock via eRecovery & wi-fi.
Huawei has Recovery and eRecovery, each has different functions.
You can use the following combinations in your phone:
- Recovery + eRecovery (stock FW)
- TWRP instead of Recovery + eRecovery
- Recovery + TWRP instead of eRecovery
aribk said:
wiping the data partition with twrp was liable to create trouble.
Q2: Same question as above.
Click to expand...
Click to collapse
Same answer as above. Formatting (not wiping) data with TWRP 3.4+ is dangerous (running stock EMUI).
Q3: All this only works on EMUI 8 as far as I know.
Q4: follow the instructions, imo.
P.S.: as you can see, mobile Linux projects such as Ubuntu Touch, postmarketOS or Sailfish OS work only partially on Hua/Ho phones,but we already talked about that .

-Alf- said:
Same answer as above. Formatting (not wiping) data with TWRP 3.4+ is dangerous (running stock EMUI).
Click to expand...
Click to collapse
Re-reading your answer above, I see I'd like to double check: Is this dangerous only if you are running stock EMUI, or would it also be dangerous to use TWRP 3.4+ to format the data partition when you wish to run a different system on the device, as in my case?

aribk said:
aribk said:
or would it also be dangerous to use TWRP 3.4+ to format the data partition when you wish to run a different system on the device, as in my case?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hard to say, no one has experience with different system . But I don't think it matters - see Mr. Frax3r's post above (and read carefully bro ).

I'm bumping the thread, few improvements are made for android 13.

Thank you for the update.
I have modified Phenix_4.9.235-phenix-1.0 rebased on Harmonyos to make it permissive which make most A13 GSIs boot normally on my phone. I have attached the updated one.

Frax3r said:
After you set up your phone and made sure you don't need stock recovery, flash magisk:
Click to expand...
Click to collapse
magisk-patched stock recovery remains functional, available and usable.

[GUIDE][A107M] BL Unlock, Twrp, ROMs and Magisk

I am not responsible for any damage to your device, when you root you lose the Warranty
This guide collects A107F development info, but with the files ported to the A107M.
Thanks to the Galaxy A10s Development team for the original files.
You need to be on Android 10, if you are on android 11, there are tutorials to downgrade.
[BootLoader Unlock]
- Backup all your media, this process will delete your internal media including music and photos
- Go to developer settings and enable [OEM Unlock]
- Reboot to download mode (Turn off, press VOL- & VOL+ and connect the USB)
- When prompted, press and hold VOL + to enter bootloader unlock mode
- Press VOL + to confirm you want to unlock bootloader, this will wipe your data
- If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
- Go through the initial setup. Skip through all the steps since data will be wiped again later when we flash TWRP and magisk
- Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. This step is MANDATORY
- Perfect! Your bootloader now accepts unofficial images in download mode.
[Twrp Install]
At this point, you will need to install Odin on your PC.
Bootloader unlocked is OBLIGATORY.
On your MicroSD, put the "A10s-encryption-disabler.zip" file.
Boot to download mode, load "VBMeta" file in AP and "TWRP Ported to A107M" file in BL
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL+, VOL - and POWER buttons at the same time
- With the USB connected, and after the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and POWER button at the same time to boot to TWRP Recovery
NOTE: TWRP on this phone is not perfect, after booting to it, the screen will remain black after the Samsung logo disappears, simply wait 10 seconds and press the power button 2 times to have acces to it.
- After booting to TWRP successfully, go to WIPE in TWRP
- At the bottom, you should see an option to FORMAT DATA. After you select it, you will be asked to type "yes" in your keyboard. If you do not see this, you probably selected the wrong option.
- After formatting data, flash the "A10s-encryption-disabler.zip" with TWRP. This is done to avoid future bootloops.
- Optional, flash "Magisk.zip" if you want to keep on Stock ROM with root.
- After doing this, boot back to system and you are done
- Wait patiently for the device to boot for the first time
[Custom ROMs Install]
Bootloader unlocked and TWRP isntalled are OBLIGATORY.
Most of the GSI ROMs of this forum works fine on this device.
Only download a64 ROMs, do not confuse with ARM64.
On your MicroSD, put the ROM image.
- Boot to TWRP
- Go to Wipe > Advanced
- Wipe ONLY the System partition
- Go to Install
- At the bottom, select option "Install Image"
- Search for your GSI. It should be something that ends in .img. If it ends in .xz instead, you need to extract the image first
- Optional, if you want Root, flash the "Magisk.zip" file
- Go to recovery main menu
- Go to Reboot
- Reboot to Recovery
- After that, go to Wipe and perform a Factory Reset
- Reboot to System and enjoy!
[Downloads]
>Everything you will need<

I had a problem in Odin an "RQT-CLOSE" error occurred

Lukas203 said:
I had a problem in Odin an "RQT-CLOSE" error occurred
Click to expand...
Click to collapse
I GOT THE SAME THING WHATS HAPPENNING?

Worked perfectly on a107m with binary 6

Alexander_SlowD said:
Worked perfectly on a107m with binary 6
Click to expand...
Click to collapse
If it worked for you, what procedure did you follow? What rom did you use for bit 6? what tools did you use?

It worked for me at first time I see TWRP menu but I didnt followed the instructions correctly , I've tried to do it by myself after that , then I got a unnoficial bootloader error and RQT_CLOSE error when trying to do the Odin process again .
Any working solution are welcome and I will be thankfully , please !

Luciannus said:
It worked for me at first time I see TWRP menu but I didnt followed the instructions correctly , I've tried to do it by myself after that , then I got a unnoficial bootloader error and RQT_CLOSE error when trying to do the Odin process again .
Any working solution are welcome and I will be thankfully , please !
Click to expand...
Click to collapse
The TWRP is slready working for me , now I trying the Magisk part , I did this on Android 11 binary 6 trough A107MUBS6CWA3_ZTO firmware ...

Develop Bugs

welcome