Develop Bugs

[HELP] I lost my IMEI number.

Hello,
Can anyone upload the APDB & BULGInfo file, I need that file to fix the IMEI issue?
Thanks in advance

It's already in the stock ROM.
Under diagnose folder you find modemdb and apdb files.

No one is gonna give those files. They are unique to each device. Send it back.

IMEI is written on the box.. I remember there was a tool for writing the same to a Karbonn phone ROM (Considering both are MediaTek).. Not sure if that will work...
Can't remember the tool name, was really a bad tool but did the job well..

i have lost my imei number and i fixed mine
1) install all drivers for Lenovo k8 Note
2) take back of our all your data
4) Switch of the Mobile and remove memory card/ SIM cards
3) Download following :
a) SP Flash tool
b) META MAUI 4G/3G
c) SN Writer-latest version
4) Start SP Flash Tool
a) Click on "Download Agent" button Choose MTK All in One file
b) Click on Scatter File button, select file from Firmware folder, where you downloaded the Stock Rom File.
Th stock ROM file may be in ZIP format. Please. Please Unzip it. Then u can see Scatter File. Please wait it to load the file. Do not connect your phone yet
c) Select Firmware Upgrade Mode in SP Flash tool. Click on OPTION in SP flash tool, select Download, Check USB CHECKSUM and STORAGE CHECKSUM box
d) Click DOWNLOAD BUTTON
e) press volume up key for 8-10 seconds and connect phone and download starts automatically.
f) Wait it to finish until you saw OK message on screen.
Disconnect your phone.
DONE
THE FOLLOWING METHOD IS FOR ONLY WHEN YOU LOST YOUR IMEI NUMBER OR WHEN YOU ACCIDENTALLY SELECTS FORMAT+DOWNLOAD OPTION IN SP FLASH TOOL OR ACCIDENTALLY DELETED
PLEASE NOTE IF YOU SELECT FORMAT AND DOWNLOAD THAT WILL DELETE ALL OF THE CONFIGURATION DETAILS OF YOUR MOBILE (IMEI NUMBER/ WIFI ADDRESS/ BT ADDRESS/ SERIAL NUMBER)
SHUTDOWN YOUR MOBILE AND REMOVE SD CARD/ SIM CARDS
OPEN SP FLASH TOOL
CLICK ON CHOOSE OPTION IN DOWNLOAD AGENT. it’s in the SP Flash tool Folder
CHOOSE MTK ALL IN ONE FILE. It’s in the SP Flash tool Folder
CLICK ON “CHOOSE” OPTION IN SCATTER- LOADING FILE" AND CHOOSE "SCATTER FILE" FROM FIRMWERE FOLDER WHERE YOU UNZIP THE STOCK ROM
SELECT "OPTION" BUTTON IN SP FLASH TOOL.CLICK “DOWNLOAD “OPTION. UNCHECK "USB CHECKSUM" and "STORAGE CHECKSUM" box. PLEASE DON'T CHANGE ANY OTHER OPTION
CLICK DOWNLOAD BUTTON
PRESS VOLUME UP BUTTON OF YOUR MOBILE FOR 8-10 seconds
CONNECT YOUR PHONE TO PC VIA USB CABLE AND DOWNLOAD WILL START AUTOMATICALLY
AFTER SEEING OK MESSAGE ON SP FLASH TOOL DISCONNECT YOUR PHONE
AGAIN SELECT OPTION BUTTON IN SP FLASH TOOL.CLICK DOWNLOAD OPTION--CHECK/ SELECT USB CHECKSUM and STORAGE CHECKSUM box.
THIS TIME CHOOSE FIRMWARE UPGRADE OPTION IN SP FLASH TOOL
CLICK DOWNLOAD OPTION
AGAIN PRESS VOLUME UP BUTTON OF YOUR MOBILE FOR 8-10 SECONDS
CONNECT YOUR PHONE
AFTER SEEING OK MESSAGE ON SP FLASH TOOL .DISCONNECT YOUR PHONE
DON'T START YOUR PHONE YET
START META MAUI 4G/3G (AS ADMINISTRATOR)
PRESS RECONNECT DEVICE OPTION
CONNECT YOUR PHONE AND PRESS POWER ON BUTTON
YOU CAN SEE META MODE ON YOUR MOBILE SCREEN
WAIT FOR IT UNTIL THE BLINKING BUTTON TURN INTO YELLOW
GO TO FIRMWARE FOLDER OR WHERE YOU UNZIPPED THE STOCK ROM AND NAVIGATE TO DIAGNOSIS FOLDER
SELECT MODEMDB.ZIP FILE AND EXTRACT IT
SELECT IMEI OPTION IN META MAUI
CLICK ON CHANGE NV RAM DATABASE
CLICK YES OPTION TO SELECT MANUALLY (it will show some errors. just ignore it)
GO TO LOCATION WHERE YOU EXTRACTED MODEMDB.ZIP FILE AND SELECT MDDB_InfoCustomAppSrcP_MT6797_S00_MANNING_V20_1_ulwctg_n.EDB FILE
Warning: don't use any other modemdb file or u will not be able to write the NVRAM DATABASE and IMEI number. You have to select the same modem.db file of the firmware your flashing your phone with
IT WILL SHOW ERROR ABOUT VERSION. JUST IGNORE IT.
YOU SEE MESSAGE IN MAUI NVRAM DATABASE FILE INIT SUCCESSFULLY
ENTER YOUR IMEI NUMBER (don’t worry the last digit of imei number will automatically generated
I STRONGLY ADVISE TO ENTER YOUR ORIGINAL IMEI NUMBERS
CLICK DOWNLOAD TO FLASH
CLICK ON SAVE FILE.FOR FUTURE USE AND PUT IT IN SAFE PLACE WHERE U CAN EXCESS IT.
WHEN FINISHED CLICK DISCONNECT" OPTION
PHONE WILL SHUTDOWN. (DON'T WORRY)
DISCONNECT YOUR PHONE
DON'T START YOUR PHONE YET
OPEN SN WRITTEN TOOL
CLICK ON SYSTEM CONFIG
CHECK ONLY WIFI AND BLUETOOTH AND DON’T SELECT ANYTHING ELSE
CLICK ON MD1_DB
GO TO LOCATION WHERE YOU EXTRACTED MODEMDB.ZIP FILE AND SELECT MDDB_InfoCustomAppSrcP_MT6797_S00_MANNING_V20_1_ulwctg_n.EDB FILE
NAVIGATE TO DIAGNOSIS FOLDER
SELECT APDB.TAR EXTRACT IT
CLICK ON AP_DB FILE AND GO TO LOCATION WHERE YOU EXTRACTED APDB.TAR FILE AND SELECT APDB_MT6797_S01_alps-mp-n1.mp9_W17.39
SELECT SAVE OPTION
SELECT CHANGE COMPORT OPTION TO USB VCOM
CHANGE TARGET TYPE TO SMART PHONE
CLICK ON START
ENTER YOUR 12 DIGIT BLUETOOTH / WIFI ADDRESS
FOR BLUETOOTH U CAN USE ANY 12 DIGIT RANDOM NUMBERS LIKE
9A8B7C6D5E4F
CONNECT YOUR PHONE
IT WILL TAKE 2-3 MINUTES U WILL SEE MESSAGE SAYING PASS
DONE!!!!

Just a heads up. Altering the imei outside of restoring is not allowed.
Editing the imei is illegal in many countries and as such any tools or talks about it are banned from this site.
Sent from my SAMSUNG-SM-G891A using Tapatalk

I have successfully written slot 1 original imei from the box, but how I write imei for second slot of my Lenovo k8 note XT1902-3 (MT7679)

ShamimK said:
I have successfully written slot 1 original imei from the box, but how I write imei for second slot of my Lenovo k8 note XT1902-3 (MT7679)
Click to expand...
Click to collapse
use sn flash tool

everything is ok until the last step , I got SPMETA_DLL::META_MAUI_DB_INCONSISTANT

solved
samihussein said:
everything is ok until the last step , I got SPMETA_DLL::META_MAUI_DB_INCONSISTANT
Click to expand...
Click to collapse
Solved , I used an older version of the SN Tool

sarab2017 said:
1) install all drivers for Lenovo k8 Note
2) take back of our all your data
4) Switch of the Mobile and remove memory card/ SIM cards
3) Download following :
a) SP Flash tool
b) META MAUI 4G/3G
c) SN Writer-latest version
4) Start SP Flash Tool
a) Click on "Download Agent" button Choose MTK All in One file
b) Click on Scatter File button, select file from Firmware folder, where you downloaded the Stock Rom File.
Th stock ROM file may be in ZIP format. Please. Please Unzip it. Then u can see Scatter File. Please wait it to load the file. Do not connect your phone yet
c) Select Firmware Upgrade Mode in SP Flash tool. Click on OPTION in SP flash tool, select Download, Check USB CHECKSUM and STORAGE CHECKSUM box
d) Click DOWNLOAD BUTTON
e) press volume up key for 8-10 seconds and connect phone and download starts automatically.
f) Wait it to finish until you saw OK message on screen.
Disconnect your phone.
DONE
THE FOLLOWING METHOD IS FOR ONLY WHEN YOU LOST YOUR IMEI NUMBER OR WHEN YOU ACCIDENTALLY SELECTS FORMAT+DOWNLOAD OPTION IN SP FLASH TOOL OR ACCIDENTALLY DELETED
PLEASE NOTE IF YOU SELECT FORMAT AND DOWNLOAD THAT WILL DELETE ALL OF THE CONFIGURATION DETAILS OF YOUR MOBILE (IMEI NUMBER/ WIFI ADDRESS/ BT ADDRESS/ SERIAL NUMBER)
SHUTDOWN YOUR MOBILE AND REMOVE SD CARD/ SIM CARDS
OPEN SP FLASH TOOL
CLICK ON CHOOSE OPTION IN DOWNLOAD AGENT. it’s in the SP Flash tool Folder
CHOOSE MTK ALL IN ONE FILE. It’s in the SP Flash tool Folder
CLICK ON “CHOOSE” OPTION IN SCATTER- LOADING FILE" AND CHOOSE "SCATTER FILE" FROM FIRMWERE FOLDER WHERE YOU UNZIP THE STOCK ROM
SELECT "OPTION" BUTTON IN SP FLASH TOOL.CLICK “DOWNLOAD “OPTION. UNCHECK "USB CHECKSUM" and "STORAGE CHECKSUM" box. PLEASE DON'T CHANGE ANY OTHER OPTION
CLICK DOWNLOAD BUTTON
PRESS VOLUME UP BUTTON OF YOUR MOBILE FOR 8-10 seconds
CONNECT YOUR PHONE TO PC VIA USB CABLE AND DOWNLOAD WILL START AUTOMATICALLY
AFTER SEEING OK MESSAGE ON SP FLASH TOOL DISCONNECT YOUR PHONE
AGAIN SELECT OPTION BUTTON IN SP FLASH TOOL.CLICK DOWNLOAD OPTION--CHECK/ SELECT USB CHECKSUM and STORAGE CHECKSUM box.
THIS TIME CHOOSE FIRMWARE UPGRADE OPTION IN SP FLASH TOOL
CLICK DOWNLOAD OPTION
AGAIN PRESS VOLUME UP BUTTON OF YOUR MOBILE FOR 8-10 SECONDS
CONNECT YOUR PHONE
AFTER SEEING OK MESSAGE ON SP FLASH TOOL .DISCONNECT YOUR PHONE
DON'T START YOUR PHONE YET
START META MAUI 4G/3G (AS ADMINISTRATOR)
PRESS RECONNECT DEVICE OPTION
CONNECT YOUR PHONE AND PRESS POWER ON BUTTON
YOU CAN SEE META MODE ON YOUR MOBILE SCREEN
WAIT FOR IT UNTIL THE BLINKING BUTTON TURN INTO YELLOW
GO TO FIRMWARE FOLDER OR WHERE YOU UNZIPPED THE STOCK ROM AND NAVIGATE TO DIAGNOSIS FOLDER
SELECT MODEMDB.ZIP FILE AND EXTRACT IT
SELECT IMEI OPTION IN META MAUI
CLICK ON CHANGE NV RAM DATABASE
CLICK YES OPTION TO SELECT MANUALLY (it will show some errors. just ignore it)
GO TO LOCATION WHERE YOU EXTRACTED MODEMDB.ZIP FILE AND SELECT MDDB_InfoCustomAppSrcP_MT6797_S00_MANNING_V20_1_ulwctg_n.EDB FILE
Warning: don't use any other modemdb file or u will not be able to write the NVRAM DATABASE and IMEI number. You have to select the same modem.db file of the firmware your flashing your phone with
IT WILL SHOW ERROR ABOUT VERSION. JUST IGNORE IT.
YOU SEE MESSAGE IN MAUI NVRAM DATABASE FILE INIT SUCCESSFULLY
ENTER YOUR IMEI NUMBER (don’t worry the last digit of imei number will automatically generated
I STRONGLY ADVISE TO ENTER YOUR ORIGINAL IMEI NUMBERS
CLICK DOWNLOAD TO FLASH
CLICK ON SAVE FILE.FOR FUTURE USE AND PUT IT IN SAFE PLACE WHERE U CAN EXCESS IT.
WHEN FINISHED CLICK DISCONNECT" OPTION
PHONE WILL SHUTDOWN. (DON'T WORRY)
DISCONNECT YOUR PHONE
DON'T START YOUR PHONE YET
OPEN SN WRITTEN TOOL
CLICK ON SYSTEM CONFIG
CHECK ONLY WIFI AND BLUETOOTH AND DON’T SELECT ANYTHING ELSE
CLICK ON MD1_DB
GO TO LOCATION WHERE YOU EXTRACTED MODEMDB.ZIP FILE AND SELECT MDDB_InfoCustomAppSrcP_MT6797_S00_MANNING_V20_1_ulwctg_n.EDB FILE
NAVIGATE TO DIAGNOSIS FOLDER
SELECT APDB.TAR EXTRACT IT
CLICK ON AP_DB FILE AND GO TO LOCATION WHERE YOU EXTRACTED APDB.TAR FILE AND SELECT APDB_MT6797_S01_alps-mp-n1.mp9_W17.39
SELECT SAVE OPTION
SELECT CHANGE COMPORT OPTION TO USB VCOM
CHANGE TARGET TYPE TO SMART PHONE
CLICK ON START
ENTER YOUR 12 DIGIT BLUETOOTH / WIFI ADDRESS
FOR BLUETOOTH U CAN USE ANY 12 DIGIT RANDOM NUMBERS LIKE
9A8B7C6D5E4F
CONNECT YOUR PHONE
IT WILL TAKE 2-3 MINUTES U WILL SEE MESSAGE SAYING PASS
DONE!!!!
Click to expand...
Click to collapse
Did it work for Lenovo vibe k5 plus, I lost my phone's IMEI

samihussein said:
Solved , I used an older version of the SN Tool
Click to expand...
Click to collapse
Have you done this for oreo rom?

GUIDE: How to unbrick your Zenfone 6 (ZS630KL)

Hello.
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Note: Unlocked bootloader is not required to do any of the actions described in this guide.
Disclaimer: I'm in no way responsible for the actions you perform and whatever happens to your device due to these actions. Proceed at your own risk.
Prerequisites:
Service firmware. Can be downloaded here. It's an older build, but it will do the trick and it's the only one I could find freely available at the time of writing. Only for WW SKU
Zip for your desired build. Can be found here.
- Note: For this guide, my desired build will be WW-17.1810.1910.63, which is a special case, as you will need to flash in the following order: Service Firmware -> WW-16.1220.1909.194 -> WW-17.1810.1910.63. In other cases, unless noted otherwise in a description of the build on the ASUS website, Service Firmware -> Desired build will suffice.
Platform tools of Android SDK. Latest package can be downloaded from: Windows | Linux. Somewhat optional but good to have.
Step 1 - Preparing the environment
This is not required but for the sake of simplicity and keeping everything in one place, create a folder and name it whatever you like, for example ASUS or Unbrick
Create a sub-folder inside the folder you've created in the previous step, call it service_firmware, download and unzip service firmware into this folder
Download files for the desired builds from the above link. For this specific case, WW-16.1220.1909.194 and WW-17.1810.1910.63.
3.a If you have microSD card, transfer zip file for the desired build into its root and insert the card into the phone.
3.b. If you do not have a microSD card, download and unzip platform tools mentioned in the prerequisites as you will need adb to flash firmware/s via sideload
Step 2 - Flashing service firmware
Connect your phone via USB
Enter fastboot mode via one of the methods:
1.1. Turn off your device, then turn it on while holding down the power and volume up buttons at the same time. Release the power button when it powers up (keep holding the volume up button)
1.2. If you have platform tools, you can do adb reboot fastboot
Open CMD (windows) | Terminal (unix)
CD into the folder with service firmware from item #2 from the step above.
Make sure your phone is detected by typing fastboot devices
Ensure battery is at least 20% charged. Aside from normal means, it's possible to check the battery charge via fastboot oem get-batcap.
Sample output: (bootloader) bat cap = 35, which means that the battery is 35% charged.
IMPORTANT NOTE BEFORE CONTINUING:
By default, flashing with one of the scripts wipes your userdata, in other words, it performs a factory reset.
It is possible to avoid userdata wipe (although not encouraged) but keep in mind, unless you flash your current build after flashing service firmware, your phone will not boot up.
If you absolutely would like to preserve your userdata, even if for the sake of backing it up before doing a factory reset, you have to edit the flashall script in the following way:
Windows: Open flashall.cmd in your favorite text editor, go to line #298 and change it from fastboot -w to REM fastboot -wand save the changes.
Unix: Open flashall.sh in your favorite text editor, go to line #275 and change it from $fastbootcmd -w to #$fastbootcmd -w and save the changes.
Once again, this is not encouraged as it can potentially cause issues later on. You've been warned.
Run the script
1. 1. Windows: In the CMD you opened earlier, type flashall.cmd
1. 2. Unix: In the Terminal you opened earlier, type ./flashall.sh
Note: An obvious note, do not disconnect your device from your PC while flashall script is running. Your device will reboot a few times during the execution.
Once script outputs format logdump... and the phone reboots, service firmware will be flashed.
Step 3 - Upgrade to your desired build
Enter Recovery mode via one of the following methods:
1.1. If your phone is turned on and USB debugging is enabled, use command adb reboot recovery
1.2. While in fastboot mode, navigate to Recovery Mode using Volume Up/Down buttons and select with a single press of a Power button
1.3. While in fastboot mode, issue one of the following commands : fastboot reboot recovery or fastboot oem reboot-recovery
Once in Recovery Mode, you have 2 ways to proceed:
A: Update from SD card
A.1. Select Apply update from SD card option
A.2. Navigate your SD card and select UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip
A.3. Confirm your choice with a single press of the Power button
A.4. Once you're back to the menu of Recovery Mode, reboot by selecting Reboot system now and enter Recovery Mode once again via any of the above methods
A.5. Select Apply update from SD card option again
A.6. Navigate your SD card and select UL-ASUS_I01WD-ASUS-17.1810.1910.63-1.1.1-user.zip
A.7. Confirm your choice with a single press of the Power button
A.8. Once you're back to the menu of Recovery Mode, select Reboot system now
B: Update through ADB Sideload
B.1. Select Apply update from ADB option
B.2. In your CMD/ Terminal, issue command adb sideload "UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip"
B.3. Once you're back to the menu of Recovery Mode, reboot by selecting Reboot system now and enter Recovery Mode once again via any of the above methods
B.4. Select Apply update from ADB again
B.5. In your CMD/ Terminal, issue command adb sideload "UL-ASUS_I01WD-ASUS-17.1810.1910.63-1.1.1-user.zip"
B.6. Once you're back to the menu of Recovery Mode, select Reboot system now
Note: Like I've mentioned earlier, these steps are specifically for build WW-17.1810.1910.63. If your target build does not require another build for an update, you can skip steps A.4 to A.7 or B3 to B5
That's pretty much it. If you followed the steps above correctly, you should once again have a running phone with your desired build of firmware.
If you have any questions, do not hesitate to ask.
Cheers.

Hello i've a question (sorry for my bad English). This morning my phone was bricked (red message logo), and with this tuto i remove this logo and i found my original recovery.
But when i want to install firmware from recovery with SDcard option, i've a message no SDcard found and impossible to install firmware. (even after several tries)...
If i reboot my phone i have android logo bootloop...
Can you help me???
https://drive.google.com/file/d/1GStfEgZFpb66JRaAmjeYOKmyn9d8WcPz/view?usp=sharing
https://drive.google.com/file/d/1FSRZfI1vNAyDQDZaLDGrHyiC-lImsYhr/view?usp=sharing
Thank you and Happy New Year...

Thanks for the link to that service firmware!

_Kuroi_ said:
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Cheers.
Click to expand...
Click to collapse
Thanks a lot mate, you made my day!
Please, one question: can you tell me, if both slots (A & B) are flashed by this method?

Thanks!
Thank you so much!
I've wanted to go back to stock for so long, but I haven't been able to find a stock ROM. I've even contacted ASUS support and they couldn't even get it! Thank you so much for the download and for the guide, you've made my week. I'll be smiling every time I use my phone thanks to you!

Great guide. I have a soft bricked device after flashing Lineage 16.0 recovery. Have a boot loop and can't get to recovery. I realise the mistake was flashing the recovery as should have just booted it.
Has anyone else had success with this on a Zenfone 6?

For those who need it; managed to resolve by downloading the stock firmware from Asus, extracting the boot.img and flashing it. Back working.
Didn't try the guide but this is quicker in this scenario if you have flashed a custom recovery to the boot partition. There is no separate recovery partition so this soft bricked the device, overwriting boot with recovery (I followed the guide here for LineageOS which is ill advised) . Should be booting the recovery rather than flashing, or booting into stock recovery and using the installer zip for your custom recovery.
Steps to recover:
1. Download stock firmware from Asus - make sure you use the same firmware version installed on the device or you may find it will boot but some hardware such as WiFi or others may not work.
2. Extract the archive and then you need to extract the boot.img from payload.bin - see this article and use the payload dumper
3. Flash your boot.img with fastboot flash boot boot.img
4. Reboot
Device should restart and boot up. Now to see why TWRP and LineageOS custom recoveries won't boot.

Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.

This worked for me, but I'm still in CSC FastBoot Mode and when Android boots, I'm asked to insert a previous pin, which nothing works. Any advice?

kenturky said:
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
Click to expand...
Click to collapse
hey, did you manage to fix this? i'm having the exact same problem

sapientsaxonsaboo said:
1. Download stock firmware from Asus - make sure you use the same firmware version installed on the device or you may find it will boot but some hardware such as WiFi or others may not work.
2. Extract the archive and then you need to extract the boot.img from payload.bin - see this article and use the payload dumper
3. Flash your boot.img with fastboot flash boot boot.img
4. Reboot
Device should restart and boot up. Now to see why TWRP and LineageOS custom recoveries won't boot.
Click to expand...
Click to collapse
I tried to install latest firmware from
https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_BIOS/
everything goes fine but it shows till this moment:
fastboot flash boot_b boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.295s]
Writing 'boot_b' FAILED (remote: 'Flashing is not allowed for non-official image')
any suggestions ?

kenturky said:
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
Click to expand...
Click to collapse
Taylor Moon said:
hey, did you manage to fix this? i'm having the exact same problem
Click to expand...
Click to collapse
Try flashing latest image of Android 9 and then flash Android 10

Can somebody please help me with my problem?
So I was able to get my hands on a new 8gb/512gb matte black version of this. Was setting up the phone, updated to Android 10 first before transfering sms, call logs and updating apps. Went to turn off the phone to insert my SIM card and now the phone won't turn on. It vibrates every time I press the power button but then nothing. Currently it's connected to the supplied charger with the LED light lit red. It was already charging while I was using it, had about 70% battery before I switched it off. I've tried volume down + power button for 10 seconds, LED light turns off and it vibrates, and it keeps vibrating every 10 seconds when it's connected to the charger (doesn't keep vibrating when it's not connected). Can feel the area between the fingerprint reader and camera pretty hot during this. Volume up + power doesn't work either. Any ideas?
Click to expand...
Click to collapse
Also, the phone gets detected when I connect it to my laptop but I can't do an "adb reboot" or "adb reboot fastboot" as it says the "error: device is not found."
I left it on charge overnight and the LED changed from red to green too.
Any help would be greatly appreciated.

CVonV said:
Can somebody please help me with my problem?
Also, the phone gets detected when I connect it to my laptop but I can't do an "adb reboot" or "adb reboot fastboot" as it says the "error: device is not found."
I left it on charge overnight and the LED changed from red to green too.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
When you connect it to your laptop, go to device manager and check what it is detected as.

_Kuroi_ said:
When you connect it to your laptop, go to device manager and check what it is detected as.
Click to expand...
Click to collapse
I can't seem to find any listing that would correspond to the phone under the Ports section :/

CVonV said:
I can't seem to find any listing that would correspond to the phone under the Ports section :/
Click to expand...
Click to collapse
Maybe upload a screenshot of the devices listing?

_Kuroi_ said:
Maybe upload a screenshot of the devices listing?
Click to expand...
Click to collapse
I thought it would've been listed in the Ports section but it's right at the top under "Android Device" as "Android ADB Interface". I believe I have the correct Qualcomm drivers installed.
Attached screenie also shows device not found when I try an "adb reboot" in command prompt.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hmm, I half expected it to be listed as QDLoader 9008, but then it would be under serial ports.
Try fastboot commands instead of adb and also try holding power + vol down for 10-15 seconds

Great guide @_Kuroi_ , I will be trying it out soon. The service rom you are using is pretty old. So I grabbed the last P update service firmware (WW-16.1220.1909.194) and the latest Q build I could get currently (WW-17.1810.2002.133). I have a subscription to one of the paid firmware sites for reasons like this. This way people have more options and it will simplify most people's updating because they can go from the new P service rom to any Q ota. Q firmware doesn't really make sense until it's not being updated anymore but it's here just in case someone finds it useful. If there is some incompatibility in the future or something that requires a newer update I will grab it then. If there isn't I will grab the last firmware once Q is stopped being updated.
WW-16.1220.1909.194
Here
WW-17.1810.2002.133
Here
WW-17.1810.2009.176
Here
Feel free to update your guide to incorporate these all I ask is a credit in the OP for providing it.

After running ./flashall.sh I get the following output:
Done.
target reported max download size of 805306368 bytes
File system type is raw !!!
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'userdata'...
OKAY ( 0.266s)
Sending 'userdata' (1888 KB)...
OKAY ( 0.067s)
Writing 'userdata'...
OKAY ( 0.003s)
Erasing 'metadata'...
OKAY ( 0.027s)
Finished. Total time: 0.799s
Rebooting...
(I changed square brackets to round brackets in the output because otherwise it wouldnt let me post this comment because of bbcode)
I don't seem to have a recovery partition by the end of it and "adb devices" doesn't show me anything.
Does anyone know what might have gone wrong?

[Mi A2][Unlock Bootloader][TWRP][ROM] Ressurection Remix v8.6.5 | Xiaomi Mi A2 (jasmine_sprout)

Greetings Readers,
Today you will learn how to unlock bootloader of your Mi A2 device along with flashing latest(as per now) TWRP(v3.5.0) subsequently flashing the latest(as per now) Resurrection remix OS(v8.6.5).
Your Phone's warranty would void. So you might wanna think again before going forward.
All of your device data would be wiped so create a backup beforehand.
Your device might get stuck in bootloop.
Your device might get damaged.
I won't be responsible for any ruckus you create.​
Pre-requisites:
- Your phone's battery must be charged at least to 70%.​- Keep your PC plugged into power as well.​- Be confident.​Lets Begin​
Things Needed:
- Xiaomi Mi A2​- PC(Windows recommended)​- Data Cable​​Files Needed​
File NameDownload LinkInstructionsRROS-Q-Final v8.6.5Resurrection Remix Downloads- Scroll down until you see a file: RROS-Q-Final-8.6.5-20201215-jasmine_sprout-Official-gapps.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Now click on this file name to start the download.
*Gapps included in this ROM file​twrp v3.5.0Download twrp-3.5.0_9-0-jasmine_sprout.img-Click on the blue colored text: Download twrp-3.5.0_9-0-jasmine_sprout.img
twrp-installer v3.5.0Download twrp-installer-3.5.0_9-0-jasmine_sprout.zip- Click on the blue colored text: Download twrp-installer-3.5.0_9-0-jasmine_sprout.zip
platform-tools v31.0.0SDK Platform Tools release notes | Android Developers- Scroll down a bit and under Downloads section click on blue colored text: Download SDK Platform-tools for windows
- Now click on checkbox and then click on the download button to start the download:
Mi Unlock Tool v4.5.813.51miflash_unlock-en-4.5.813.51.zip-​Dm Verity Force Encrypt Disabler v11.02.2020Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip-​
*all the above given download links are from the respective official websites. So, download them all on your PC.
Preparing Mi A2​
Enabling OEM Unlock and USB Debugging:
- Navigate to Settings > About phone.​~ Tap on Build number 7 times.​- Navigate to Settings > System > Developer options.​~ Enable the 'OEM unlocking' and 'USB debugging' switch.​- Switch off your phone.​- Press the Power button and Volume Down button simultaneously, until you see the fastboot screen.​- Connect the phone to your PC using USB data cable.​
Working on PC​
Installing drivers:
- Extract the 'miflash_unlock-en-4.5.813.51.zip' file.​- Inside this file double click on 'miflash_unlock.exe' file.​*we are not installing this tool. We are just using it for installing our device drivers.​​
​- On the top right corner click on the settings gear icon.​​
​- Now click on 'Check' button.​​
​*it will ask for Administration Access twice.​- Click on 'Yes' both the times.​*a new dialogue box appears asking you to connect your device again.​- Unplug your device and connect it again and the drivers will get installed.​​Unlocking Bootloader:
- Extract the 'platform-tools_r31.0.0-windows.zip' file.​- Inside this file will be a folder platform-tools. Open it.​- Now in the address bar type 'cmd' and hit enter.​​
​​*we did this in order to open cmd to this location. So that our future commands are accessible.​- In the cmd window type the command:​
Code:
fastboot devices
​*it will display our device, something like this:​​
​​/* In case your device is not displayed.​Try installing drivers again. */​- Enter the command:​
Code:
fastboot oem unlock
​*this unlocks the bootloader temporarily​/* A screen pops up on our phone.​Navigate using volume buttons and select using power button.​Our phone reboots.​Set up everything haphazardly.​Navigate to Settings and enable Developer options.​Enable USB debugging in Developer options.​Switch off your phone and boot into fastboot mode again. ​Enter the command fastboot devices in order to check if our device is successfully connected. */​- Enter the command:​
Code:
fastboot oem unlock_critical
​*this will unlock our bootloader permanently​/* Once again a screen pops up on our phone asking for a confirmation.​Confirm it and phone reboots.​Once again set it up haphazardly.​Enable Developer options and USB debugging subsequently.​Boot into fastboot mode again. */​- Enter the command:​
Code:
fastboot oem device-info
*this command will confirm if our device' bootloader has been unlocked or not​​
Installing twrp:
-Enter command:​
Code:
fastboot format userdata
*this command wipes Internal Storage of our phone​-Enter command:​
Code:
fastboot format cache
*this command wipes cache of our phone​-Now enter the command fastboot boot and drag and drop the 'twrp-3.5.0_9-0-jasmine_sprout.img' file into cmd and hit enter.​*we did this so that command file will know the location of our twrp img file and hence execute the command​​/* Our phone will boot into recovery mode.​Transfer 'twrp-3.5.0_9-0-jasmine_sprout.img', 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip', 'RROS-Q-Final-8.6.5-20201215-jasmine_sprout-Official-gapps.zip' to Mi A2's Internal storage. */​
Working on Phone​​- Tap on Install > Install Image(bottom right corner) button.​- Select 'twrp-3.5.0_9-0-jasmine_sprout.img' file.​- Now in 'Select Partition to Flash Image:' scroll down and select the 'Install Recovery Ramdisk' option.​- Swipe right to flash.​- Press back once flashing is complete.​*temporary installed twrp in Slot B​​- Go to Home > Wipe > Advanced Wipe.​- Tap on every checkbox except the 'Internal Storage'.​- Swipe right to wipe.​*we wiped the stock rom from Slot B​​- Go to Home > Reboot > Slot A.​- Go to Home > Install.​- Select the file 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip' and swipe right to flash.​*we temporary installed twrp in Slot A​​- Go to Home > Reboot > Recovery.​- Tap on Wipe > Advanced Wipe.​- Tap on every checkbox except the 'Internal Storage'.​*we wiped stock rom from Slot A​​- Go to Home > Install.​- Select the 'RROS-Q-Final-8.6.5-20201215-jasmine_sprout-Official-gapps.zip' ROM file and swipe right to flash.​*this might take some time​- When flashing is finished tap on 'Wipe Cache/Dalvik' button.​*we flashed RROS rom in Slot A​​- Go to Home > Install.​- Select the 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip' and swipe right to flash it again.​*we installed twrp in Slot A again as it got wiped when we flashed our rom​​- Go to Home > Reboot > Slot B.​- Go to Home > Install.​- Select the 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip' file and swipe right to flash.​- Head back to Home > Wipe > Format Data.​- Type 'yes' and tap on the Tick button.​- Go to Home > Reboot > Recovery.​- Go to Mount and tap on 'Enable MTP' button in the lower right corner (Do not press it if it's showing 'Disable MTP').​- Now transfer the 'Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip' file into your phone's internal storage using your PC.​- Go to Install and select the file 'Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip' and swipe right to flash.​*we installed twrp permanently in slot B​- Select the 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip' and swipe right to flash it again.​- Head to Home > Reboot > System.​​​Congratulations we have successfully installed RROS on our Mi A2​
How to boot into recovery:
Method 1: using Software
- Navigate to Settings > Resurrection tools > System > Power dialog.​- Scroll down and under the 'BUTTONS' section, enable the 'Enable advanced restart' switch.​-Now long press the power button and then select Advanced from the menu to see all the options.​Method 2: using Hardware
- Switch off the phone.​- Press Power button and Volume Up button simultaneously.​- Just as you see Android Boot Splash Screen, press the Volume Up button twice.​​Bugs & Fixes​
BugsFixesCamera isn't recording videos.- Head to Camera Settings.
- In 'Video quality' select 'FHD 1080p, 30fps' option.Phone stuck on boot splash screen when battery drains completely.
*this might occur for the very first time only​- Boot into recovery using Power + Volume Up buttons.
- On twrp home screen, go to Reboot > Power Off.
- Switch On your phone by long pressing power button.Sometimes excessive tweaking delays device wake up.- Reboot SystemUI.
- Let the phone sit for a minute.Camera sounds not turning off.- Root your device using latest Magisk app.
- Now, install the module 'Disable screenshot and camera sounds'.
- Reboot your device.​
Special Thanks to:
RROS Team for providing such a wonderful ROM.
TeamWin - TWRP for providing the twrp files.
@Zackptg5 for the Disable Dm-Verity file.
And to every person who made this possible.
Thankyou for Reading​

You can turn on developer option turn on oem unlock. You can register on miui. Provide your mobile details they will give you unlock code. You can say you are developer and you want to unlock it.
Unlock code for android smartphone simcard
How to unlock android smartphone, what is mobile locking & how to check smartphone is locked or not. How to get sim network unlock code for mobile, different kind of cellphone carrier unlock codes. Requirement of generating sim unlock code from imei.
mobile-cellphones.blogspot.com

YOU TOMUCH WRITE, HUHH....
MY DEVICE XIAOMI MI A2 RAM 6 gb ROM 128 GB, THIS MONT I DOWNLOAD AND INSTAL ALL KIND JANK AND FINALLY I WIPE ALL THEN YESTERDAY HERE I DOUNLOAD RROS 8.6.7 OFFICIAL VANILLA,
HOW I INSTALL IT ON WIPED MI A2?
I USE APP RUBBIT XIAOMI ADB/FastbootTools.exe ONLY,
I INSTALL IMAGES OF OFICIAL FIRMWARE Q AND PBRP recovery NOT TO boot BUT TO Recovery, UNBELIVABLE BUT IT HAPPEN. AFTER FEW TIMES I ACCESS TO SDcard OF MI A2 FROM MY TOSHIBA FAKE NOTEBOOK OF YEAR 2008 WITH FAKE WINDOWS7 AND I COPY FILE RROS 8.6.7 FIRMWARE TO TWRP FOLDER CREATED WITH PBRP, ALSO FOLDER Tools FROM PBRP recovery.img
I INSTALL RROS TO a AND TO b, ALSO INSTALL Magisk, Supersu, AND NOT ONES, I DID it UNTILL SUCCESS.
I WANT TO TELL THAT IS AMAZING ROM NO GAPS I LOVE IT, BUT IT CHEAT ME WITH UPDATE TO LATEST RROS 8.6.9 YOU SEE 69 POSE WITH GAPPS, HUHH..
I AGAIN DELETE WIPE ALL RROS AND REINSTALL RROS 8.6.7 VANILLA NO WITH GOOGLE 69.
PLESE SEND TO VANILLA UPDATES WITH VANILLA AND TO RROS WITH GAPPS SEND UPDATES RROS GAPPS, IT NOT THE SAME.
AND PLEASE GIVE FILE boot.img FOR RROS 8.6.7 or 8.6.0 or 8.6.5 BECOUSE MAGISK NEED FILE boot.img AND I DO NOT KNOW WHY YOU SMART DEVELOPERS NEVER SHARE FILE boot.img WITH PRASED ROMS, THANK YOU.
NOW AFTER INSTALLING YOUR TWRP CAN NOT START IT STACK ON LOGO, NOT GOOD YOUR TWRP,
NEED boot_patched.img OF THIS RROS.
OK, I TRY AGAIN INSTALL TWRP 3.5.2 TO Recovery AND AGAIN INSTALL TWRP 3.5.2 TO boot AND INSTALL MAISK AND MagiskManagerRecovery TO ANABLE ROOT AND REBOOT AND IT STILL RUN RR LOGO
* * * * *
RROS 8.6.7 THE BEST ROM IT HAVE ANYTHING WE NEED EVEN BUTTON REMAPER IN THE SETTING, ALL MY BELOVED GAMES CAN RUN WITH THIS RROS ANDROID 10, EVEN J2MeRunner AND IT GAME LIKE Heroes Lore Wind of Soltia AND SuperWaterBomber, ALSO J2MeLoader WORKING AND CAN RUN ALL Java Jar Games, RROS THE BEST BUT I NEED ROOT FOR MY FRIEND LuckyPatcher
* * * * *
SO MANY TALKING ABOUT TOOLS AND adb TO UNLOCK BOOTLOADER,
I AM SORRY I AM SMARTER OR ALL AROUND MAD, JUST GO DEVELOPER OPTION AND TURN ON UNLOCK BOOTLOADER.
AND IN Xiaomi ADB/FastbootTools CLICK UNLOCK AND IT SAY ALREADY UNLOCKED THEN FLASH ANYTHING. I DID IT USING GARBAGE JUNK NOTEBOOK TOSHIBA J70 CHINES CLONE AND THERE SMARTERS PEOPLE USING LATEST WINDOWS AND PC ADVICE TO US adb MANY JUNK ZIP FILES I USE APP SIZE 2.9 MB AND NOTHING ELSE.
* * * * *
GOOD/ GOOD TWRP 5.3.2 AND PATCH ALSO GOOD BUT I MISTAKE AND INSTALL TWRP TO a AND TO b NOW I HAVE TWRP IN a AND b,
PHONE BOOTLOOP WHEN START a, AND WORKING OK WHEN START b, I NO UNDERSTAND WHY NOT YET I GET ROOT, SUPERSU NO WORKING, MAGISK EVERY 3 OPTIONS YES BUT INSTALLED SHOW N/A, I INSTALL MAGISK FROM TWRP HUNDRED TIMES AND NOT YET ROOT, IT ASKED ME FOR boot.img
MAYBE NEED PATCH TWRP.. AND INSTAL IT IN 101 TIME..

eleven.co said:
Greetings Readers,
Today you will learn how to unlock bootloader of your Mi A2 device along with flashing latest(as per now) TWRP(v3.5.0) subsequently flashing the latest(as per now) Resurrection remix OS(v8.6.5).
Your Phone's warranty would void. So you might wanna think again before going forward.
All of your device data would be wiped so create a backup beforehand.
Your device might get stuck in bootloop.
Your device might get damaged.
I won't be responsible for any ruckus you create.​
Pre-requisites:
- Your phone's battery must be charged at least to 70%.​- Keep your PC plugged into power as well.​- Be confident.​Lets Begin​
Things Needed:
- Xiaomi Mi A2​- PC(Windows recommended)​- Data Cable​​Files Needed​
File NameDownload LinkInstructionsRROS-Q-Final v8.6.5Resurrection Remix Downloads- Scroll down until you see a file: RROS-Q-Final-8.6.5-20201215-jasmine_sprout-Official-gapps.zip
View attachment 5226269
- Now click on this file name to start the download.
*Gapps included in this ROM file​twrp v3.5.0Download twrp-3.5.0_9-0-jasmine_sprout.img-Click on the blue colored text: Download twrp-3.5.0_9-0-jasmine_sprout.imgView attachment 5226271twrp-installer v3.5.0Download twrp-installer-3.5.0_9-0-jasmine_sprout.zip- Click on the blue colored text: Download twrp-installer-3.5.0_9-0-jasmine_sprout.zipView attachment 5226273platform-tools v31.0.0SDK Platform Tools release notes | Android Developers- Scroll down a bit and under Downloads section click on blue colored text: Download SDK Platform-tools for windows
View attachment 5226281
- Now click on checkbox and then click on the download button to start the download:
View attachment 5226285Mi Unlock Tool v4.5.813.51miflash_unlock-en-4.5.813.51.zip-​Dm Verity Force Encrypt Disabler v11.02.2020Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip-​
*all the above given download links are from the respective official websites. So, download them all on your PC.
Preparing Mi A2​
Enabling OEM Unlock and USB Debugging:
- Navigate to Settings > About phone.​~ Tap on Build number 7 times.​- Navigate to Settings > System > Developer options.​~ Enable the 'OEM unlocking' and 'USB debugging' switch.​- Switch off your phone.​- Press the Power button and Volume Down button simultaneously, until you see the fastboot screen.​- Connect the phone to your PC using USB data cable.​
Working on PC​
Installing drivers:
- Extract the 'miflash_unlock-en-4.5.813.51.zip' file.​- Inside this file double click on 'miflash_unlock.exe' file.​*we are not installing this tool. We are just using it for installing our device drivers.​​View attachment 5226331​​- On the top right corner click on the settings gear icon.​​View attachment 5226333​​- Now click on 'Check' button.​​View attachment 5226335​​*it will ask for Administration Access twice.​- Click on 'Yes' both the times.​*a new dialogue box appears asking you to connect your device again.​- Unplug your device and connect it again and the drivers will get installed.​​Unlocking Bootloader:
- Extract the 'platform-tools_r31.0.0-windows.zip' file.​- Inside this file will be a folder platform-tools. Open it.​- Now in the address bar type 'cmd' and hit enter.​​View attachment 5226371​​*we did this in order to open cmd to this location. So that our future commands are accessible.​- In the cmd window type the command:​
Code:
fastboot devices
​*it will display our device, something like this:​​View attachment 5226381​​/* In case your device is not displayed.​Try installing drivers again. */​- Enter the command:​
Code:
fastboot oem unlock
​*this unlocks the bootloader temporarily​/* A screen pops up on our phone.​Navigate using volume buttons and select using power button.​Our phone reboots.​Set up everything haphazardly.​Navigate to Settings and enable Developer options.​Enable USB debugging in Developer options.​Switch off your phone and boot into fastboot mode again. ​Enter the command fastboot devices in order to check if our device is successfully connected. */​- Enter the command:​
Code:
fastboot oem unlock_critical
​*this will unlock our bootloader permanently​/* Once again a screen pops up on our phone asking for a confirmation.​Confirm it and phone reboots.​Once again set it up haphazardly.​Enable Developer options and USB debugging subsequently.​Boot into fastboot mode again. */​- Enter the command:​
Code:
fastboot oem device-info
*this command will confirm if our device' bootloader has been unlocked or not​​View attachment 5226413​
Installing twrp:
-Enter command:​
Code:
fastboot format userdata
*this command wipes Internal Storage of our phone​-Enter command:​
Code:
fastboot format cache
*this command wipes cache of our phone​-Now enter the command fastboot boot and drag and drop the 'twrp-3.5.0_9-0-jasmine_sprout.img' file into cmd and hit enter.​*we did this so that command file will know the location of our twrp img file and hence execute the command​​/* Our phone will boot into recovery mode.​Transfer 'twrp-3.5.0_9-0-jasmine_sprout.img', 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip', 'RROS-Q-Final-8.6.5-20201215-jasmine_sprout-Official-gapps.zip' to Mi A2's Internal storage. */​
Working on Phone​​- Tap on Install > Install Image(bottom right corner) button.​- Select 'twrp-3.5.0_9-0-jasmine_sprout.img' file.​- Now in 'Select Partition to Flash Image:' scroll down and select the 'Install Recovery Ramdisk' option.​- Swipe right to flash.​- Press back once flashing is complete.​*temporary installed twrp in Slot B​​- Go to Home > Wipe > Advanced Wipe.​- Tap on every checkbox except the 'Internal Storage'.​- Swipe right to wipe.​*we wiped the stock rom from Slot B​​- Go to Home > Reboot > Slot A.​- Go to Home > Install.​- Select the file 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip' and swipe right to flash.​*we temporary installed twrp in Slot A​​- Go to Home > Reboot > Recovery.​- Tap on Wipe > Advanced Wipe.​- Tap on every checkbox except the 'Internal Storage'.​*we wiped stock rom from Slot A​​- Go to Home > Install.​- Select the 'RROS-Q-Final-8.6.5-20201215-jasmine_sprout-Official-gapps.zip' ROM file and swipe right to flash.​*this might take some time​- When flashing is finished tap on 'Wipe Cache/Dalvik' button.​*we flashed RROS rom in Slot A​​- Go to Home > Install.​- Select the 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip' and swipe right to flash it again.​*we installed twrp in Slot A again as it got wiped when we flashed our rom​​- Go to Home > Reboot > Slot B.​- Go to Home > Install.​- Select the 'twrp-installer-3.5.0_9-0-jasmine_sprout.zip' file and swipe right to flash.​- Head back to Home > Wipe > Format Data.​- Type 'yes' and tap on the Tick button.​- Go to Home > Reboot > Recovery.​- Go to Mount and tap on 'Enable MTP' button in the lower right corner (Do not press it if it's showing 'Disable MTP').​- Now transfer the 'Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip' file into your phone's internal storage using your PC.​- Go to Install and select the file 'Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip' and swipe right to flash.​*we installed twrp permanently in slot B​- Head to Home > Reboot > System.​​​Congratulations we have successfully installed RROS on our Mi A2​
How to boot into recovery:
Method 1: using Software
- Navigate to Settings > Resurrection tools > System > Power dialog.​- Scroll down and under the 'BUTTONS' section, enable the 'Enable advanced restart' switch.​-Now long press the power button and then select Advanced from the menu to see all the options.​Method 2: using Hardware
- Switch off the phone.​- Press Power button and Volume Up button simultaneously.​- Just as you see Android Boot Splash Screen, press the Volume Up button twice.​​Bugs & Fixes​
BugsFixesCamera isn't recording videos.- Head to Camera Settings.
- In 'Video quality' select 'FHD 1080p, 30fps' option.Phone stuck on boot splash screen when battery drains completely.
*this might occur for the very first time only​- Boot into recovery using Power + Volume Up buttons.
- On twrp home screen, go to Reboot > Power Off.
- Switch On your phone by long pressing power button.Sometimes excessive tweaking delays device wake up.- Reboot SystemUI.
- Let the phone sit for a minute.Camera sounds not turning off.- Root your device using latest Magisk app.
- Now, install the module 'Disable screenshot and camera sounds'.
- Reboot your device.​
Special Thanks to:
RROS Team for providing such a wonderful ROM.
TeamWin - TWRP for providing the twrp files.
@Zackptg5 for the Disable Dm-Verity file.
And to every person who made this possible.
Thankyou for Reading​
Click to expand...
Click to collapse

THE BEST ROM THANK YOU.

ALWAYS PROBLEM UNABLE CREATE CACH OR SYSTEM SOLVED BY WIPING ALL EXEPT ENTERNAL AND INSTALLING TO RAM DISC NOT TWRP 3.5.0_9 BUT TWRP 3.2.3 AND IT FLASHING CLEARLY TO CURRENT SLOT FROM a TO a, FROM b TO b WITHOUT RED LETTERS ABOUT ERROR, SO IN ORDER to FLASH RROS AND PATCH AND MAGISK NEED TWRP 3.2.3 jasmine sprout.img
И НИКАКИХ ТАНЦЕВ С БУБНОМ,
НУЖЕН ЗАЯЦ В УШАНКЕ 2.9 mb.exe И TWRP 3.2.3, ПРОШИВКА СУПЕР

LUCY YISRAEL said:
ALWAYS PROBLEM UNABLE CREATE CACH OR SYSTEM SOLVED BY WIPING ALL EXEPT ENTERNAL AND INSTALLING TO RAM DISC NOT TWRP 3.5.0_9 BUT TWRP 3.2.3 AND IT FLASHING CLEARLY TO CURRENT SLOT FROM a TO a, FROM b TO b WITHOUT RED LETTERS ABOUT ERROR, SO IN ORDER to FLASH RROS AND PATCH AND MAGISK NEED TWRP 3.2.3 jasmine sprout.img
И НИКАКИХ ТАНЦЕВ С БУБНОМ,
НУЖЕН ЗАЯЦ В УШАНКЕ 2.9 mb.exe И TWRP 3.2.3, ПРОШИВКА СУПЕР
Click to expand...
Click to collapse
Thankyou for your suggestions and corrections. I'm glad that you did it.

[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 GSI​Note:​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.0​Note:​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 Downgrading​Sources:​
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.0​Prerequisites:​
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 GSI​Prerequisites:​
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 Encryption​Prerequisites:​
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 Downgrading​Prerequisites:​
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.
Magisk​Prerequisites:​
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.0​Prerequisites:​
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 GSI​Prerequisites:​
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 Encryption​Prerequisites:​
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 Downgrading​Prerequisites:​
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.
Magisk​Prerequisites:​
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.0​Prerequisites:​
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 GSI​Prerequisites:​
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 Encryption​Prerequisites:​
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 Downgrading​Prerequisites:​
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.
Magisk​Prerequisites:​
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) How to fix a hard bricked Redmi Note 9 (Merlin) (Hard Brick)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A how-to guide of restoring a completely bricked Redmi Note 9​
Hi, In this guide, I will teach you how to fix a hard-bricked Redmi Note 9 (merlin) and bring it back to its original state.
How does a hard-bricked Redmi Note 9 look like? it's stuck in an infinite boot loop showing only the Redmi logo,
Can't access recovery with power+vol down, can't enter fastboot, can't connect it to a computer either.
If this is your phone here's how you can solve it without the need for service.
Following this guide keep in mind that everything would be erased from your phone including custom Recovery or ROM obviously. Also the bootloader would get locked again.
(I mean at this point you either have a useless brick or a working phone, you are choosing).
This is tested by me, and it works as long as you follow the steps carefully and you don't skip anything.
(I did this on Windows 10 btw)
You gonna need to download, Python and the official Xiaomi fastboot image for Redmi Note 9. Also the zip file I'm attaching bellow. the zip file contains the MTK Drivers, SP Flash Tool, and some additional scripts like MI auth bypass etc,
Get thefastboot image from here select your version (I picked the latest global) click download scroll down where it says "type:fastboot" and click "download: full Rom" the file name should look like this "merlin_images....tgz" or "merlin_global_images....tgz", etc, NOT miui_Merlin.zip,
Get python from the official website site, I tested it with 3.9.7 but the latest version should work fine. Now, you have all the necessary files to start.
Let the phone's battery die so the boot looping completely ends. (else you'll get error STATUS_EXT_RAM_EXCEPTION (0xC0050005) when using SP Flash Tool). ( I also tried it with a full battery and still worked so idk for sure how necessary this step is).
Install Python select the "add to PATH" option, you can test if it was installed correctly by opening cmd and writing "python" or "py" it should output the python version.
Extract the attached zip file and the fastboot image each into their folders.
Enter the MTK Driver folder Install the MTK Driver for MTK SP flash tool.MTK_Driver_Auto_Installer_SP_Drivers_20160804.exe, Reboot your computer.
Enter the python folder, run the "install pyusb pyserial json5.bat" when it's done close the terminal.
Enter the driver folder, this folder contains a USB to COM driver for MTK Devices, right-click the "cdc-acm.inf" click install.
Enter the libusb folder, run the libusb-win32-devel-filter-1.2.6.0.exe file, click next,next...install, when it's done it would prompt you to launch "filter installer wizard" click finish, when the wizard shows up, select "Install a device filter" it would show you your connected USB devices,
Get your phone and a USB cable, connect the USB cable to your computer,while holding the volume up button on your phone connect your phone to the computer (Based on community feedback you might need to hold both up and down volume buttons AND power button!) once your phone turns on you would see your phone listed as "MediaTek USB Port" at the libusb filter installer before your phone reboots click at the "MediaTek USB Port" and then click install if you don't do it on time, your phone will get disconnected because of rebooting, try again re-plugging your phone. once you click install, You should get a pop-up message saying "...device filter successfully installed for MediaTek USB port..." click ok and exit, then remove your phone from the computer.
Enter the bypass folder (This folder contains scripts to bypasses the Mi auth) double click the "1ST RUN THIS.bat" when it says "waiting for device" hold volume up and plug your phone into the computer (btw: You can let the button when it's recognized by the script). now most likely it would say "RuntimeError: unexpected output, expected 0xfd got 0xfe", if it does close the script and disconnect your phone, Try the "2ND RUN THIS.bat" when it shows "Waiting for device" hold volume up and connect your phone to the computer, wait till the console recognizes your phone, (At this part it might take few tries to make it work, try reconnecting your phone without holding any buttons or try holding volume down while reconnecting your phone) Once it gets recognized it would output "Found port = COM3" and Protection disabled. At this part your phone has stopped boot looping which is good but, DO NOT TOUCH YOUR PHONE, DO NOT DISCONNECT IT FROM THE COMPUTER, set your phone aside, and continue with the guide.
Enter the SP Flash Tool folder run the flash_tool.exe at the Download-Agent click choose and select the DA_6765_6785_6768_6873_6885_6853.bin file which is included in the SP flash tool folder.
At the Authentication File, click choose and select the auth_sv5.auth included in the SP flash tool folder.
At the Scatter-loading File, click choose, go to the fastboot image extraction folder (Step 4) then enter the images folder and select the MT6768_Android_scatter.txt file (Fastbootimage/images/MT6768_Android_scatter.txt)
On the drop-downbox below the "Authentication File" label change the option from Download Only to Firmware Upgrade.
At the toolbar above click Options -> Option... go to Connection check the UART option and set the Baud rate to 921600, make sure the com port option is set to com 3, then close the window.
Click Download with the green arrow, now wait till it finished flashing your phone this would take quite of time, at this part DO NOT TOUCH ANYTHING LET IT FINISH TO AVOID ANY CURROPTION ON YOUR PHONE. (If you get "Error : STATUS_STOR_LIFE_EXHAUST" go to options-> general and uncheck Storage life cycle check).
When it's done it would show you a pop-up window "Download Ok" with a green background and a checkmark, click the X to close, and now you can also close the SP Flash tool app.
Disconnect your device from your computer and press the power buttonto start your phone, connect it to a charger or back to the computer since there was no charge so it won't die suddenly now.
Your phone now should boot normally showing the MIUI logo, because its first boot it would take few minutes for the phone to boot, wait patiently and you would see the "first setup" screen.
That's it! You successfully brought back to life a hard-bricked Redmi Note 9 (merlin). A huge weight now has lifted from you hf.
Credits:
Bypass script and payload included in the attachment file is provided by (chaosmaster, xyzz) github

Very good guide, my friend.
Thank you very much for details and contribution

My device was brick yesterday, OTA update pixel plus ui rom and get boot loop at redmi logo. I do exactly your tutor but in step 11 my device is not recognized. Any solution for me? Thanks.

aries.1482 said:
My device was brick yesterday, OTA update pixel plus ui rom and get boot loop at redmi logo. I do exactly your tutor but in step 11 my device is not recognized. Any solution for me? Thanks.
Click to expand...
Click to collapse
If you did step 9 it should recognize it, try to reboot your computer if you didn't already. Also your phone would be visible only for a second before it gets disconnected so you have to act fast.

vagelis199 said:
If you did step 9 it should recognize it, try to reboot your computer if you didn't already. Also your phone would be visible only for a second before it gets disconnected so you have to act fast.
Click to expand...
Click to collapse
Your window is 32 or 64 bit, I use windows 10 64 bit and did all step, one by one but no effect.

Finally, done it. I found this:
- Hold both vol up and down when plug in so the device recognize.
- You must choose right fastboot image (origin stock rom), if not devices can't boot in to miui rom cause bootloader locked after sp flash
And at last, thank you very much, you saved my day.

aries.1482 said:
Finally, done it. I found this:
- Hold both vol up and down when plug in so the device recognize.
- You must choose right fastboot image (origin stock rom), if not devices can't boot in to miui rom cause bootloader locked after sp flash
And at last, thank you very much, you saved my day.
Click to expand...
Click to collapse
Cool ill update the guide!

Hi, My device is recognized as "Qualcom HS-USB QDLoader 9008" not the "MediaTek USB Port" on step 11 and it seems not recognized on step 12. Do you have any solutions for me. Thanks!

lionfishes said:
Hi, My device is recognized as "Qualcom HS-USB QDLoader 9008" not the "MediaTek USB Port" on step 11 and it seems not recognized on step 12. Do you have any solutions for me. Thanks!
Click to expand...
Click to collapse
I think you are on a wrong guide, That's a guide for a Redmi Note 9, not the Pro version

vagelis199 said:
I think you are on a wrong guide, That's a guide for a Redmi Note 9, not the Pro version
Click to expand...
Click to collapse
My phone is Redmi Note 9. I tried to restart it yesterday and couldn't power on again. So I'm looking for some solutions to see if it can be fixed. Thanks!

lionfishes said:
My phone is Redmi Note 9. I tried to restart it yesterday and couldn't power on again. So I'm looking for some solutions to see if it can be fixed. Thanks!
Click to expand...
Click to collapse
There's no qualcomm version of Redmi Note 9

i made a mistake,when i clicked to download the fastboot at the xiaomi site,i clicked the fastboot link to download,but i didnt see that it brings you to a page where it has all the downloads again,so i stopped the operation and restarted it with the correct scatter this time.
Now im waiting to see what will happen,how long does it usually take for the spflash to finish?
Also at the bottom of spflash where it says 0b/s,emmc etc. should it stay at 0 when you start the download?
edit:
managed to make it work,one important thing for me was at the option/option,had to select com port com 3

nikosefs said:
i made a mistake,when i clicked to download the fastboot at the xiaomi site,i clicked the fastboot link to download,but i didnt see that it brings you to a page where it has all the downloads again,so i stopped the operation and restarted it with the correct scatter this time.
Now im waiting to see what will happen,how long does it usually take for the spflash to finish?
Also at the bottom of spflash where it says 0b/s,emmc etc. should it stay at 0 when you start the download?
edit:
managed to make it work,one important thing for me was at the option/option,had to select com port com 3
Click to expand...
Click to collapse
Thanks i updated the guide including this

i'm having an ERROR notification : STATUS_EXT_RAM_EXCEPTION (0xC0050005) help me

Looking for some info/help if possible: apologies i'm not trying to derail your thread.
I had bricked my RN9 but managed to unbrick and have it working ok now however I am wanting to restore it/lock the bootloader to allow for using banking apps. But I am encountering an issue. I had tried using MiFlash Tool but during the flash, I get a mismatch error and it doesn't succeed in flashing the Fastboot rom.
If i was to follow your guide from step 13, would this work for me? Or which steps do I need to skip in your list?
Thank you for any advice/help
** I finally managed to get it sorted ** used the EDL flash guide and then flashed in SPFT.
[GUIDE] How To bypass authentication and flash in EDL with NO auth for FREE
Thanks to: chaosmaster / k4y0z: GitHub / XDA xyzz / xyz`: GitHub / XDA Dinolek: GitHub / XDA How to install: 1. Download the attached file: VD171_MTK-bypass.zip. 2. Extract the file and open the folder. 3. Run and install python...
forum.xda-developers.com

vagelis199 said:
Hi, In this guide, I will teach you how to fix a hard-bricked Redmi Note 9 (merlin) and bring it back to its original state.
How does a hard-bricked Redmi Note 9 look like? it's stuck in an infinite boot loop showing only the Redmi logo,
Can't access recovery with power+vol down, can't enter fastboot, can't connect it to a computer either.
If this is your phone here's how you can solve it without the need for service.
Following this guide keep in mind that everything would be erased from your phone including custom Recovery or ROM obviously. Also the bootloader would get locked again.
(I mean at this point you either have a unless brick or a working phone, you are choosing).
This is tested by me, and it works as long as you follow the steps carefully and you don't skip anything.
(I did this on Windows 10 btw)
You gonna need to download, Python and the official Xiaomi fastboot image for Redmi Note 9. Also the zip file I'm attaching bellow. the zip file contains the MTK Drivers, SP Flash Tool, and some additional scripts like MI auth bypass etc,
Get the fastboot image from here select your version (I picked the latest global) click download scroll down where it says "type:fastboot" and click "download: full Rom" the file name should look like this "merlin_images....tgz" or "merlin_global_images....tgz", etc, NOT miui_Merlin.zip,
Get python from the official website site, I tested it with 3.9.7 but the latest version should work fine. Now, you have all the necessary files to start.
Let the phone's battery die so the boot looping completely ends. (I'm not sure if this is completely necessary but that's how I did it).
Install Python select the "add to PATH" option, you can test if it was installed correctly by opening cmd and writing "python" or "py" it should output the python version.
Extract the attached zip file and the fastboot image each into their folders.
Enter the MTK Driver folder Install the MTK Driver for MTK SP flash tool. MTK_Driver_Auto_Installer_SP_Drivers_20160804.exe, Reboot your computer.
Enter the python folder, run the "install pyusb pyserial json5.bat" when it's done close the terminal.
Enter the driver folder, this folder contains a USB to COM driver for MTK Devices, right-click the "cdc-acm.inf" click install.
Enter the libusb folder, run the libusb-win32-devel-filter-1.2.6.0.exe file, click next,next...install, when it's done it would prompt you to launch "filter installer wizard" click finish, when the wizard shows up, select "Install a device filter" it would show you your connected USB devices,
Get your phone and a USB cable, connect the USB cable to your computer, while holding the volume up button on your phone connect your phone to the computer (Based on community feedback you might need to hold both up and down volume buttons) once your phone turns on you would see your phone listed as "MediaTek USB Port" at the libusb filter installer before your phone reboots click at the "MediaTek USB Port" and then click install if you don't do it on time, your phone will get disconnected because of rebooting, try again re-plugging your phone. once you click install, You should get a pop-up message saying "...device filter successfully installed for MediaTek USB port..." click ok and exit, then remove your phone from the computer.
Enter the bypass folder (This folder contains scripts to bypasses the Mi auth) double click the "1ST RUN THIS.bat" when it says "waiting for device" hold volume up and plug your phone into the computer (btw: You can let the button when it's recognized by the script). now most likely it would say "RuntimeError: unexpected output, expected 0xfd got 0xfe", if it does close the script and disconnect your phone, Try the "2ND RUN THIS.bat" when it shows "Waiting for device" hold volume up and connect your phone to the computer, wait till the console recognizes your phone, (At this part it might take few tries to make it work, try reconnecting your phone without holding any buttons or try holding volume down while reconnecting your phone) Once it gets recognized it would output "Found port = COM3" and Protection disabled. At this part your phone has stopped boot looping which is good but, DO NOT TOUCH YOUR PHONE, DO NOT DISCONNECT IT FROM THE COMPUTER, set your phone aside, and continue with the guide.
Enter the SP Flash Tool folder run the flash_tool.exe at the Download-Agent click choose and select the DA_6765_6785_6768_6873_6885_6853.bin file which is included in the SP flash tool folder.
At the Authentication File, click choose and select the auth_sv5.auth included in the SP flash tool folder.
At the Scatter-loading File, click choose, go to the fastboot image extraction folder (Step 4) then enter the images folder and select the MT6768_Android_scatter.txt file (Fastbootimage/images/MT6768_Android_scatter.txt)
On the drop-down box below the "Authentication File" label change the option from Download Only to Firmware Upgrade.
At the toolbar above click Options -> Option... go to Connection check the UART option and set the Baud rate to 921600, make sure the com port option is set to com 3, then close the window.
Click Download with the green arrow, now wait till it finished flashing your phone this would take quite of time, at this part DO NOT TOUCH ANYTHING LET IT FINISH TO AVOID ANY CURROPTION ON YOUR PHONE.
When it's done it would show you a pop-up window "Download Ok" with a green background and a checkmark, click the X to close, and now you can also close the SP Flash tool app.
Disconnect your device from your computer and press the power button to start your phone, connect it to a charger or back to the computer since there was no charge so it won't die suddenly now.
Your phone now should boot normally showing the MIUI logo, because its first boot it would take few minutes for the phone to boot, wait patiently and you would see the "first setup" screen.
That's it! You successfully brought back to life a hard-bricked Redmi Note 9 (merlin). A huge weight now has lifted from you hf.
Credits:
Bypass script and payload included in the attachment file is provided by (chaosmaster, xyzz) github
Click to expand...
Click to collapse
Hi thanks a lot for your help. I accidentally flashed a redmi 10x miui 11, wanted to downgrade my Redmi 9 from 12.5, bad perfomance, resulting in your hard-bricked version. Flashing last fastboot version doesn't help, do i have a chance to fix it?

vagelis199 said:
Get the fastboot image from here select your version (I picked the latest global) click download scroll down where it says "type:fastboot" and click "download: full Rom" the file name should look like this "merlin_images....tgz" or "merlin_global_images....tgz", etc, NOT miui_Merlin.zip,
Click to expand...
Click to collapse
Hi and thanks for this detailed guide.
I bricked my merlin trying to root it (long history trying to get TWRP to stick)
I am now in the redmi logo loop and i am trying to follow this with great care.
however in the step above, no matter what I choose in "Yshasalger" page, i end up with a Recovery ROM and the file name contains the miui prefix as opposed to what you clearly state.
see image:
I am asking because i am scared of making more mistakes.
So i guess my question is if someone can check it happens to them (maybe the page changed since the writting of this guide)
If i should try with that ROM zip file or if there is another place i can get the proper one
I want to if possible to flash an older MIUI / Android than the latest 12 xxx / Android 11 as i find the phone to be really slow since the last OTA update.

Coroneln said:
Hi and thanks for this detailed guide.
I bricked my merlin trying to root it (long history trying to get TWRP to stick)
I am now in the redmi logo loop and i am trying to follow this with great care.
however in the step above, no matter what I choose in "Yshasalger" page, i end up with a Recovery ROM and the file name contains the miui prefix as opposed to what you clearly state.
see image:
View attachment 5476667
I am asking because i am scared of making more mistakes.
So i guess my question is if someone can check it happens to them (maybe the page changed since the writting of this guide)
If i should try with that ROM zip file or if there is another place i can get the proper one
I want to if possible to flash an older MIUI / Android than the latest 12 xxx / Android 11 as i find the phone to be really slow since the last OTA update.
Click to expand...
Click to collapse
That's because you are choosing recovery and not fastboot, choose fastboot as type scroll down it has two links for recovery and for fastboot image. Check the file name

vagelis199 said:
That's because you are choosing recovery and not fastboot, choose fastboot as type scroll down it has two links for recovery and for fastboot image. Check the file name
Click to expand...
Click to collapse
i promise i am choosing fastboot but it ends up in the recovery i have tried several different versions in case it was a file wrongly indexed.

TL|DR
Python errors, step 8 and 12 on Windows 10
Go to -> "start" and type "Manage App Execution Aliases". Go to it and turn off "Python"
=========================
Now read....
Just in case someone has trouble with step: 8
Escenario: the BAT file calls `python` and in some windows 10 this will result in a message about the windows store (Even if the path is added)
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings
but `py` works, so just edit the BAT file and replace the call for `python` with `py` it will install all the python modules with no errors.
EDIT:
This also affects step: 12
Found a solution here: https://stackoverflow.com/questions...arguments-to-install-from-the-microsoft-store
Go to -> "start" and type "Manage App Execution Aliases". Go to it and turn off "Python"
The error:
After editing the BAT file replacing `python` with `py`