Database Info

Lenovo S5 Pro - L58041 (Global) [2020.03.21]

Welcome to this little thread in which I'll provide every useful information about this device based on my and other users's experiences. If you know something, that I didn't mention, please reply to this thread in order to help out each other even more effectively. Thanks and pleasant reading!​
The Lenovo S5 Pro is a very decent mid-ranger with good specs and even better pricing. We all know, that chinese manufacturers tend to install bloatware on their products time to time. In our case, Lenovo didn't release a single update since 2018 Novemer to this device. It means, that it came out with Android 8.1 Oreo (2018 November Security Patch) and left untouched. This is even worse, than Meizu which is famous for it's neglecting policy of software updates for global users. Now, that we know all this, it's not a surprise, that we are here on our favourite developer forum.
*** General information | Links | Downloads | Credits ***​
The official global firmware is now saved and available (thanks to our forum member nikosddesign) here: download & link to the post
Everything you will possibly need (PC software, drivers, stock camera app, VoLTE modem etc...) is available in this Yandex Disk, you just have to navigate to each one. (Most of the content is in russian, since Yandex is the russian Google, but it's not hard to find the files you'll need).
The previous links and the following tutorials are only available, because suninterbru (from 4pda forums) and radiationofthenation provided these informations and the tutorials, also so much thanks to everybody on the 4pda forums, who provided useful information and files, большое спасибо!
Even though the bootloader unlock, TWRP install and rooting should not cause data loss, be careful and create a backup. You can back up only your files and data or your whole ROM, it's up to you.
Please note, that after you've unlocked your bootloader, everytime your reboot or turn on your phone a warning will pop up during the boot process for about 1 second. On Android 9.0 Pie vendor the message pops up for about 5 seconds. The warning is about the side effects of modifying the system software and it also says, that it is not recommended to store any personal data on your device anymore. Please ignore this message, since it's only popping up, because manufacturers usually don't like, if you modify your device.
Pro tip: If you keep pressing your power button for a little longer you can skip the alert and boot faster.
*** Bootloader unlock ***
Please note, that your warranty will become invalid/void after you unlock your bootloader or root your device.​
0. In your device's developer settings enable bootloader/OEM unlock and USB debugging.
1. Visit the official ZUI bootloader unlock website.
2. Enter your IMEI1 number in the first field. (You can find your IMEI numbers in Settings\About or in the dialer enter: *#06#).
3. Enter your serial number in the second field. (You can find your serial number in the fastboot menu). The one in the settings is not good in this case! (To access the fastboot menu, turn off your phone, then press the power button and after you see your screen light up, immediately press the volume down (-) button or while it's turned on and USB Debugging is enabled, simply type in the terminal/cmd ,,adb reboot bootloader").
4. In the next field enter your email adress. (Please note, that Tutanota won't work, Gmail is recommended or other not secure email providers).
5. Enter the verification numbers in the last field.
6. Tick the checkbox.
8. Click on the blue button.
7. Now check your inbox and/or spam folder, because Lenovo just sent you your custom sn.img, only for your phone.
8. Save the sn.img to your PC and install ADB drivers system-wide. (Thank you Snoop05 for your work)!
9. Open a terminal/cmd on Windows. You should be in the same directory, where your sn.img file is, with the terminal. To change directories type ,,cd your directory goes here" and hit ENTER.
10. Run the following commands:
- adb reboot bootloader
- fastboot flash unlock sn.img
- fastboot oem unlock-go
11. Congratulations! Your bootloader is now unlocked!
*** TWRP Recovery ***​1. Download the .img file from here.
2. The steps are similar to the bootloader unlocking:
- adb reboot bootloader
- fastboot flash ,,downloaded" .img
- After the flashing is done DON'T reboot to the system, instead navigate to the ,,Reboot Recovery or Recovery Reboot" option and select it. (Volume keys and power key - you know the drill) This will ensure, that the TWRP Recovery doesn't get ereased on reboot(s)!
3. After you've successfully rebooted into TWRP, you should root your device with Magisk, to prevent the recovery erasure!
*** ROOT ***​1. The good old SuperSU is no longer in the picture, but don't worry a new player is in the game. Download Magisk from here. (Thank your for your work topjohnwu)!
2. After you've downloaded the flashable .zip copy it to the main directory/root of your device.
3. Reboot to TWRP.
4. Click install, select the flashable .zip file.
5. The installation process should start.
6. Reboot, after finished.
7. Check if Magisk Manager is installed or not, if yes tap and update it.
8. If you did not succeed, please check the Magisk topic for solutions or reply to this thread.
*** Factory reset | Stock ROM | Unbrick | LOST IMEI/PERSIST/EFS | QCN BACKUP/RESTORE ***
!!! NEVER EVER TICK ,,ERASE ALL BEFORE DOWNLOAD" IN QFIL, OTHERWISE YOU WILL LOSE YOUR IMEI AND THE ABILITY TO CONNECT TO MOBILE NETWORKS !!!​
If you accidentally clicked on that option you will have to restore someone elses QCN backup. (It will not work, if you backup your own QCN and rewrite your IMEI and restore it, so do not waste your time with that)! Luckily, a member of the 4PDA forums published their qcn backup. (большое спасибо geepnozeex)! QCN backup for Lenovo S5 Pro. (I modified the link, because the original one is no longer valid)
1. Download the linked QCN file.
2. Make sure, that you are on one of the Stock ROMs, however the recommended ROM is this one.
3. You will have to be rooted to put your device in diagnostics mode. To do that, follow this tutorial.
4. You will have to edit the QCN file with HxD, in order to write your own IMEI into.
5. Open the file with HxD and search for 08 8A 76 06 06 14 57 95 32. This is the IMEI 2. You will have to insert your IMEI 2 from the box here, but first you will have to convert it into Hexadecimal numbers.
6. Convert your IMEIs into Hexadecimal numbers here.
7. You will have to rewrite and insert your values insted of the previous one.
8. Search for 08 8A 76 06 06 04 67 98 72. This is IMEI 1. Convert your IMEI 1 into Hexadecimal numbers, too and replace.
9. Save the file (Ctrl + s)
10. Open QFIL and click on Tools, then QCN Backup/Restore.
11. Choose the QCN file, you wrote your IMEI into.
12. Click on Restore QCN.
13. There is a chance, that the process/progress bar won't finish till the end. No problem, just reboot to EDL mode through TWRP/Advanced and restore the recommended stock ROM.
14. You should have everything working fine, now.
To factory reset or unbrick your device, follow this tutorial on 4PDA. [Don't panic you don't have to know russian, just follow the instructions on the pictures! To see the pictures, click on the bold text.] ,,(спойлер (+) (Инструкция по прошивке)" ~ or ~ Download any of the previously linked STOCK ROMs to your device's main folder and flash them through TWRP. Most of them are in flashable .zip formats and should work well. A simple factory reset in TWRP is recommended before installing any of the ROMs, be careful this action will erease your data from your phone!
(Please note, that most of the time you'll have to use the QPST/QFIL method, because the flashable .zip files always expect a specific vendor version, usually a lower one, so you can upgrade with flashable .zips, but possibly can't downgrade, so you have to use QFIL)!
*** GSI custom ROMs ***
Our device is arm64-aonly, so please only use according GSIs. Note, that I will link only those GSIs, which are booted successfully on my device!​
~ phhusson's official GSI list: here
~ phhusson's AOSP GSI (Android Open Source Project): here
~ developerluke's ExpressLuke GSIs: here
~ eremitein's CAOS GSI Project: here
~ eremiten's LOSQ GSI Project: here
~ igors1974's Amber GSIs: here
~ tunasahinn's and yek4perf's Tunahan's GSI builds: here
~ mrsshunt3r's albus-gsi: here
Note, that you should keep up with the developments and update your system, if needed! These are just a few GSIs, that I've tested personally on my phone, but you can always keep up with the latest news and try new GSIs out, thanks to phhusson's official GSI list!
*** How to flash an Android 10 GSI ***​
1. Download the latest custom phh-magisk from here. (Thank you developerluke and phhusson)!
2. Download the latest Disable_Dm-Verity_ForceEncrypt from here. (Thank you Zackptg5 and others)!
3. Download your desired GSI.
4. You can flash from an USB-OTG flash drive or from the storage of your phone. (I personally have a dedicated USB for this purpose).
4.1 If you are coming from stock ROM you will most likely need to Format Data in this step, because the Disabler won't be able to decrypt the data and, that will cause a stuck at the boot logo!
4.2 Reboot Recovery
5. In TWRP perform a normal factory reset
6. Flash Disable_Dm-Verity_ForceEncrypt. (Cache wipe is optional).
7. Flash your GSI image.
8. Format Data (Skip this step if you already did this in 4.1)!
9. Reboot Recovery (Skip this step, too if you already did this in 4.2)!
10. Flash Magisk-phh
(11. Wipe cache/dalvik).
12. Reboot System
13. Enjoy!
*** Possible GSI bugs ***
Please note, that bugs can differ/vary on different GSIs, the numbers are not fully accurate!
​
1. The default camera app will work, however it doesn't support HDR, panorama or portrait modes. It also can't record in 4K resolution. Freezing is also possible. ~ 50%
2. First time, when you open the camera it'll stuck on loading, but after you go back and open it again it will work flawlessly. ~ 50%
3. No audio/microphone during phone calls. ~ 15%
*** Guaranteed GSI bugs*** ​1. The infrared face unlocking will not work, only fingerprint authentication is working. ~ 100%
2. You won't be able to charge your device while it's turned off, after you plug it in, it will automatically boot up. ~ 100%
3. Auto brightness. ~ 100% (There is a fix for auto brightness below)!
*** Camera fix (GSI) ***
(If you get ,,serious camera error" or your camera freezes on HDR)​
1. Download a custom camera app, where you can manually adjust the ISO level.
2. With OpenCamera, for example you have to adjust ISO to 800 and never above, because your camera will freeze!
3. So, always keep ISO 800 or under. With these settings even HDR shots are working!
*** Auto brightness (GSI) ***​1. Download framework-res__auto_generated_rro.apk from this thread.
2. Follow the instructions, which are described in this post. (You will need to have root to use ,,su" commands).
3. Thank you MishaalRahman and kAs1m for the apk and the instructions!

Twrp disappears when restarting
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.

kcire_eae said:
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.
Click to expand...
Click to collapse
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.

Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
It didn't work, given: "fastboot: usage: unknown reboot target recovery" Sorry for the long time to answer, I only have mobile data, and from this same mobile I answer, and I use google translator, I'm from Mexico.

Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
Foto

kcire_eae said:
Foto
Click to expand...
Click to collapse
Well, it looks good. Maybe only " reboot recovery " is enough.

Halwer said:
Well, it looks good. Maybe only " reboot recovery " is enough.
Click to expand...
Click to collapse
It didn't work, friend, but I appreciate the help.

kcire_eae said:
It didn't work, friend, but I appreciate the help.
Click to expand...
Click to collapse
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?

Halwer said:
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?
Click to expand...
Click to collapse
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.

kcire_eae said:
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.
Click to expand...
Click to collapse
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.

Halwer said:
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.
Click to expand...
Click to collapse
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:

kcire_eae said:
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:
Click to expand...
Click to collapse
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.

Halwer said:
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.
Click to expand...
Click to collapse
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.

kcire_eae said:
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.
Click to expand...
Click to collapse
You should do the oreo version, if your were on the global oreo ROM. After that you can try the pie version, if nothing works don't worry you can do a backup of your data from twrp to your computer and flash a custom ROM or the chinese Pie version, which is recommended. With root access you can easily debloat the chinese ROM and with AdAway you can disable all communications pointing to chinese servers or websites. I also found these. Maybe you can give them a try.

After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" .
prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata".
rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"

kcire_eae said:
After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata" rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"
Click to expand...
Click to collapse
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.

Halwer said:
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.
Click to expand...
Click to collapse
Ohh, explain more about spying. And also if you know something about the message that Android told me when I start. I remember that I flashed twrp.img using "fastboot", and when I asked for a password to decrypt, it only allowed me to clear cache and dalvit cache (I did wipe), and when I started again I showed a message saying that I was encrypting and a percentage, just here, I interrupted the process by turning off the cell phone, and flashed again with qfil (download). So when I start I just remember that I said something about the cell phone being restored and then I could restore the copy with my Google account. So what I think is that when the message of "TO START ANDROID ENTER YOUR PASSWORD" is displayed, it may work to interrupt or perhaps to put the incorrect password many times to automatically reset or also choose "rawprogram0.xml" in qfil (but I did not dare because it deletes it the information related to the imeil and the signal or at least that says some comments ). Now there is only one who can interpret what happened and to have clearer the restoration process, the rom seems to me very much the problem of the language is solved with "more local", I am from Mexico (At & t).

good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g

nikosddesign said:
good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g
Click to expand...
Click to collapse
Thank you, I'm sure some people will find it very useful!

Hello
it's about 4gigabyte have to be patient.
i have very bad internet connection...

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

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

Amazing ?

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

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

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

Thanks for the great and detailed work..

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[ROM][A51] HAVOC OS for Samsung Galaxy A51 [CUSTOM ROM]

Hey Guys,
Before you dive in, irrespective of your reading speed read this carefully and slowly for better understanding but if you cannot focus and read it slowly then you better give up music for a few weeks.
About the Device
Before you jump in and get your hands dirty.. you should know that what you will be installing is Generic System Image, It is not specifically made for your device so if you are going to install some other GSI other than this, you might face some issues.
If you are a beginner, you should Go Through Project Treble, just for the sake of knowledge.
Also Galaxy A51 has A/B partition and Supports Project Treble though remember that Treble Devices are not same as A/B devices and Vice Versa.
Things You’ll Need
A Computer (not an iPad)
Internet [requirement around 6 gigs (4.8 gigs optional, for downloading stock Firmware, Highly Recommended)]
Samsung Galaxy A51 (will not work on A50)
Patience and a madcap attitude.
Resources
Download Odin from the link given below and extract it in a folder.
https://odindownload.com/download/Odin3_v3.13.3.zip
Adb and Fastboot Drivers
https://gsmusbdrivers.com/download/adb-fastboot-drivers/#
Samsung Drivers
https://developer.samsung.com/mobile/file/68b2dc40-3833-4a8b-b58e-32f7aca25c00
Havoc OS GSI
Havoc-OS - Browse /arm64-ab at SourceForge.net
Don’t forget to check that there is “arm64” and “ab” written on the name of the file
Other option is with Gapps (it means the rom will come with Google Play services built in
otherwise it is Vanilla Android.
GSI Flasher
(It is used for converting your img file into flashable Zip)
https://drive.google.com/file/d/1J8OlI2CCXpvAJ5FhFlR2b_y58eHQERGs/view?usp=sharing
Extract it you’ll find three folders gsi, META-INF, scripts, keep all of them inside the GSI
Flasher extracted folder.
Twerp Recovery
twrp-a51-3.5.0_10-1_ianmacd.tar | by androidhowto for Utilities (androidfilehost.com)
Do not use any other in this case you might get mounting errors.
Encryption Disabler
Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip | by androidhowto for Utilities (androidfilehost.com)
Its Show time
1. Go to settings and go to about phone, tap build number 7 times and a dialog will appear, you are now a developer.
2. Go to additional setting or search developer options in the settings search bar
3. Once in the developer settings find OEM unlock and turn in on, scroll down and also turn on USB debugging, your phone will ask the permission for accessing the data by your computer.
4. Turn off your device. Get a usb cable and connect it to your computer.
5. While phone is off first press Volume UP and Volume Down together, and then then insert the usb cable into the phone while holding the buttons wait for two seconds. a blue screen will come up telling you about consequences and life choices.
6. Long press the Volume Up Button and a new blue screen will show up asking you for unlocking the bootloader. Press Volume Up to confirm. You device will erase everything and reset itself ( Don’t forget to take backup of your Data).
7. After the setup screen appears skip everything in the setup and enable developers option and enable USB debugging in the developer options.
8. Turn off your device again and Repeat step 5.
9. Press Volume up for entering the download mode
10. Now in your computer, Install Odin and open Odin.exe you’ll find your device as comm: xx
Now click on the AP button and select the twerp you downloaded.
Press start and twerp will be installed in your device. Your device will reboot don’t let it boot to one ui, press all three buttons together and hold, as soon as the screen goes black release only the volume down button. Keep holding the Volume UP and power buttons for 3 seconds and then release, you find yourself in twerp. If you miss it repeat the process again but don’t let it boot to One Ui.
In twerp press wipe => format data =>type yes. Press home button and again go to wipe advanced select Data, Cache and Dalvik and swipe to clear.
Press home again. Go to reboot and select recovery, twerp wil reboot. Once it reboots transfer the encryption disabler to your phone and in twerp press install select the storage, sdcard or internal storage, where you have stored the file, select it and swipe to install.
Now in your computer extract the Havoc os image and rename it as “system.img”.
Extract the GSI flasher, copy system.img and paste it in the gsi folder of the GSI Flasher.
Select gsi, Meta-inf, scripts and compress them into a zip and transfer into the phone.
Now in twerp Press install, select the zip file and swipe to install. Also install Gapps or Magisk if you want (though normal magisk will have problem try install phh_magisk, discussed later).
Reboot and KABLAMO You have installed Havoc OS.
Bugs
A small random issue in Auto Brightness
If you root with magisk and install modules, after you reboot your phone will get into a bootloop. Use Phh_Magisk but I aint sure if it’ll work or not Your call madcap.
NONE OF THE FILES IN THIS TUTORIAL HAVE ANYTHING TO DO WITH ME. If SOMETIHING HAPPENS I AM NOT RESPONSIBLE. ONLY DO IT AT YOUR OWN RISK.
Troubleshooting.
If you find errors in twerp, such as unable to mount vendor or system_root, or data. Then you got to install the stock One Ui Back again, therefore it is highly recommended to keep with yourself the stock firmware. You will need It. And it is 4.78 gigs. You can download it from
Model : SM-A515F - Galaxy A51 — Samfrew.com
To reinstall the stock firmware first extract it and the open odin and repeat steps 8 and 9, once your device is detected in Odin press the respective buttons and select the respective files such as for BL button select the file With BL in the name. Do it for buttons, BL, AP(once you select the file it will take long for it load into odin so do not panic and let it load, it might become unresponsive but use patience and wait.)CP , CSC. Click on start and you’ll have ONE Ui back on your device.
To Lock the bootloader repeat steps 5 and 6.
If you still want more stability and Control You can install a different Kernel NDataX from (@Hendamanu) https://forum.xda-developers.com/m/hendramanu.11224917/

Thanks for your contribution

How To Guide [GUIDE][UNLOCK][ROOT] How to unlock bootloader, flash ArrowOS v11.0 ROM and root Xiaomi Poco X3 Pro

If you've recently purchased a Xiaomi Poco X3 Pro, but were on the fence about using it until an AOSP ROM became available then you're in luck. Kudos to @kubersharma for his contribution by providing us the first official AOSP release, ArrowOS v11.0 [vayu].
Now, throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. These are fully detailed instructions to make it easier for newbs.
I've spent the better part of my day figuring all of this stuff out so hopefully you won't go through the trouble I did. PLEASE DO NOT PM ME FOR HELP. REPLY TO THIS GUIDE BELOW, THANKS. NOW LET'S BEGIN!!!
UNLOCK BOOTLOADER
1. Unlock the bootloader with Xiaomi Unlocker tool.
a. Be aware this process will factory reset the device before proceeding.
b. Download the Mi Unlock app onto your PC. Extract the contents within the zip file into an empty folder then run the app.
c. Register for Xiaomi account and sign in with your Mi Account.
d. Your Mi Account must be added to your Mi Settings
Sign into your Mi Account on the device.
Go to Settings –> About Phone –> tap on MIUI version (For POCO) until it says Developer options is enabled.
Back out of About Phone, Additional Settings –> Developer options –> Mi Unlock status.
Agree, then "Add account and device".
e. Shut down your phone manually, and hold Vol down + Power button to enter Fastboot mode.
Download and install the latest Xiaomi USB Drivers or here (or Google's latest USB drivers for Windows if all else fails) for your PC.
Connect the device to the computer via USB cable, and confirm that your phone shows up recognized as "Android Bootloader Interface" (in Device Manager), and click "Unlock" in the Unlock app.
NOTE: If Windows does not recognize the device due to it automatically installing the wrong "Kedacom Device Driver" then you will have to manually install the drivers for "Android ADB Interface/Android Bootloader Interface".
f. After your first initial unlock attempt, you MUST wait 168 hours before unlock process can fully complete.
Wiping the device or removing the Mi account from the device could result in the timer being reset.
g. After the waiting period expires, click "Unlock" in the Unlock app. You will notice the phone will restart followed by subsequent different screens during the phone's boot sequence including the "POCO" screen which now displays an "open lock icon" at the top, indicating your bootloader unlock attempt and will eventually end up on a "This device is locked" screen where you have to confirm you are the device owner by entering your Mi Account password to "activate this device"; connect to your WiFi prior to doing so if the device lacks an active sim card.
FLASH CUSTOM RECOVERY, DECRYPTION DISABLER, & ROM THEN ROOT
2. Download the Official ArrowOS v11.0-vayu fastboot ROM for POCO X3 Pro [direct link here].
a. NOTE: ArrowOS requires MIUI V12.0.4.0 firmware so it recommended to downgrade to this version before flashing ArrowOS otherwise the ROM may not boot.
b. Choose the GApps build type which "includes Play services and now some AOSP apps have been replaced with GApps... All GApps packages and other[sic] files [were] extracted from original firmware images for Pixel4XL (coral)."
3. [OPTIONAL] Download the latest version of Encryption Disabler then copy it along with the fastboot ROM into a folder named 'TWRP' on the root of your microSD.
4. Ensure USB Debugging is already enabled on your device (in Settings –> Additional Settings –> Developer options).
5. Remove any screen unlock (i.e., fingerprint, PIN, pattern or password) in MIUI.
6. Power off device and put it in Fastboot mode (Vol down + Power button).
7. Download the latest SDK Platform Tools from Google for adb compatibility and create a folder called "adb" in the root of the "C:\" drive.
a. Extract the files adb, AdbWinApi.dll, AdbWinUsbApi.dll, and fastboot into the folder.
b. Ensure the latest USB drivers are installed for your PC, connect the device to the computer via USB cable, and confirm that your phone shows up recognized as "Android Bootloader Interface".
c. Launch "Command Prompt" on your PC and run the command:
cd C:/adb
To show a list of devices (including your phone) connected to your PC, enter the command:
fastboot devices
8. Download the unofficial Pbrb (test3) recovery file (PitchBlack Recovery Project 3.1.0 unofficial) by Alex Besida and copy it into the ADB install folder and rename it to "recovery.img".
9. Flash custom recovery file in CMD, run commands:
fastboot flash recovery "recovery.img"
fastboot boot recovery.img
10. Your device should automatically boot into custom recovery. At this point, the microSD will become accessible from recovery or the PC, but the device's internal storage will not be which makes using a microSD card much more imperative for this process since the recovery is in early access development.
a. Go to Wipe –> Format Data, type "yes" to perform data wipe; Back out to the main menu.
b. Go to Install –> Navigate to the TWRP folder on the microSD (via "external_sd").
Select "Arrow-v11.0-vayu-OFFICIAL-20210424-GAPPS.zip" and flash the ROM, but do not change any of the checkboxes that show up before doing so.
Format data (not wipe) before rebooting into the new ROM.
NOTE: At most it takes around 1 minute to boot back up.
11. [OPTIONAL] Power off the device and boot back into recovery.
a. Go to Install –> Navigate to the TWRP folder on the microSD.
Select " Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip" and flash it, but do not change any of the checkboxes that show up before doing so.
NOTE: This will disable forced encryption of data partition for better performance and internal SD + Data mounting in TWRP. It's not needed for the ROM to work, but due to disabling encryption it compromises security.
Reboot into the new ROM.
12. After going through the phone's boot sequence, you'll be presented with the initial phone setup process onscreen where you can begin recovering your data.
13. Go to Settings –> About phone –>tap on Build number until it says Developer options is enabled.
a. Back out to Settings –> System –> to access Developer options –> Enable USB Debugging.
14. Installing Magisk via custom recovery will fail in the background, resulting in an unresponsive "POCO" screen which is caused by installer scripts not being able to properly detect the correct device info or the recovery environment does not meet its expectation. In this case, you will need to use the Patch Image method as it is guaranteed to work 100% of the time. Installing Magisk through custom recoveries on modern devices is no longer recommended due to this reason.
a. Pull down the Notification Bar from the top of the screen and change "Charging this device via USB" to "File Transfer".
b. Open " Arrow-v11.0-vayu-OFFICIAL-20210424-GAPPS.zip " and copy "boot.img" to the phone's internal storage.
c. Download the latest version of Magisk (Magisk v22.1) and copy it to the phone's internal storage and use the native "Files" app to install the apk.
NOTE: Magisk binaries (ZIP) are now included within Magisk Manager APK file. Now you don’t have to download it separately. You can install the .apk file or rename its extension to .zip then flash it through custom recovery / TWRP.
d. Launch Magisk from the app drawer and go to "Install" under Magisk –> "Select and Patch a File," select the "boot.img" you copied internally –> "LET'S GO".
e. Copy the generated patched file to the ADB folder and flash it via fastboot by running the following commands:
cd C:/adb
fastboot flash boot boot.img
f. Reboot into the new ROM and voila!
fastboot reboot
g. Use an app such as Root Checker or BusyBox Checker (from the Play Store) to confirm root status.
h. To bypass/restore SafetyNet validation, open the Magisk app, go to Settings (cogwheel icon) and enable MagiskHide.

SIDENOTES:
These are either my comments or other user's comments that may be considered helpful as it relates to ArrowOS
Picture guide unlock bootloader, flash custom ROMs & root Xiaomi Poco X3 Pro (Credits to @pl1992aw)
Using TWRP to install OTA Updates
Installing OTA updates
Stability of 'PitchBlack Recovery Project' Recovery
How to verify SafetyNet status
Feel feel to let me know of other threads or comments that are also related to installing ArrowOS.

Excellent guide
My suggestions in terms of improvements:
- 7-day waiting time before unlocking: I would mention that wiping the device or removing the Mi account from the device could result in the timer being reset;
- DFE/Encryption Disabler: it's optional, not needed for the ROM to work and thanks to disabling encryption it compromises security;
- Firmware: Arrow OS requires MIUI V12.0.4.0 firmware, so before flashing Arrow OS it's recommended to downgrade MIUI to this version, otherwise the ROM might not boot
In the future, once more custom ROMs come out, it should be easy to turn this guide into general flashing instructions instead and not just for Arrow OS, which would be a great resource to have here

kamild_ said:
Excellent guide
My suggestions in terms of improvements:
- 7-day waiting time before unlocking: I would mention that wiping the device or removing the Mi account from the device could result in the timer being reset;
- DFE/Encryption Disabler: it's optional, not needed for the ROM to work and thanks to disabling encryption it compromises security;
- Firmware: Arrow OS requires MIUI V12.0.4.0 firmware, so before flashing Arrow OS it's recommended to downgrade MIUI to this version, otherwise the ROM might not boot
In the future, once more custom ROMs come out, it should be easy to turn this guide into general flashing instructions instead and not just for Arrow OS, which would be a great resource to have here
Click to expand...
Click to collapse
Fair enough, thanks for the suggestions. I can add them in.

Thanks for this detailed guide! I'm currently on MIUI 12.0.2 - do you know if I have to update to 12.0.4 first or if I can follow your guide directly?

Aulig said:
Thanks for this detailed guide! I'm currently on MIUI 12.0.2 - do you know if I have to update to 12.0.4 first or if I can follow your guide directly?
Click to expand...
Click to collapse
Yes, you have to update to MIUI 12.0.4.0 before flashing.

How stable is the PBRP Beta? Great Guide btw

DeblaGaming said:
How stable is the PBRP Beta? Great Guide btw
Click to expand...
Click to collapse
More stable than other unofficial custom recoveries such as OrangeFox, especially when it comes to functionality. Based on my experience using OrangeFox, it failed to flash anything that was already present on my microSD, but PBRP worked OOB w/ no issues first time, and allowed me to copy over files onto the microSD while the device was in recovery while simultaneously being connected to my PC. Thanks btw.

AusVGM said:
Yes, you have to update to MIUI 12.0.4.0 before flashing.
Click to expand...
Click to collapse
Thank you, I did that now and then followed the guide (without disabling encryption as that's an important feature to me). Super easy to follow even though I haven't been modding a lot these past years. Worked perfectly, thanks @urbanman2004
Tip: make sure to check safetynet with an app and not magisk, as described in the thread linked regarding magisk hide

Aulig said:
Thank you, I did that now and then followed the guide (without disabling encryption as that's an important feature to me). Super easy to follow even though I haven't been modding a lot these past years. Worked perfectly, thanks @urbanman2004
Tip: make sure to check safetynet with an app and not magisk, as described in the thread linked regarding magisk hide
Click to expand...
Click to collapse
Thanks for the compliment... I didn't feel the need to include how someone could check their device's SafetyNet status, but the app I use is called SafetyNet Helper Sample in the Play Store.

Very detailed instruction thumbs up...
My questions
1. For miui requirement the MIUI V12.0.4.0 , is it free or need specific version like chinese or europe or asia or america for more clearly
2. In future when twrp or custom recovery available , can we just flash the rom via recovery as simple as that. Like other phone

bla.tiga said:
Very detailed instruction thumbs up...
My questions
1. For miui requirement the MIUI V12.0.4.0 , is it free or need specific version like chinese or europe or asia or america for more clearly
2. In future when twrp or custom recovery available , can we just flash the rom via recovery as simple as that. Like other phone
Click to expand...
Click to collapse
Thanks for the compliment. To answer your questions:
1) Any version of MIUI V12.0.4.0 will do.
2) To flash future OTA updates (ROMs), it will require flashing the "compatible recovery" (vayu ArrowOS Recovery) in fastboot mode, rebooting the device then followed by installing the OTA update once it becomes available and letting it flash automatically.

hello all,
I have flashed vanilla version of ArrowOS, and magisk...
could somebody help me with installing microG for VANILLA build ROM? I'm new to microG stuff, so I don't really know from where should I install, what version etc.
some apps are not running as they require Google play services

I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.

as400l said:
I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.
Click to expand...
Click to collapse
Best that your question be taken up w/ the devs.

as400l said:
I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.
Click to expand...
Click to collapse
So I have some breaking news:
I can confirm that the latest unofficial alpha version of TWRP (TWRP-3.5.1-vayu-Nebrassy-1) is capable of decrypting and reading internal storage. Due to this advancement, I can also confirm that ArrowOS OTA updates will officially work using TWRP. There is NO NEED TO USE ANY OTHER CUSTOM RECOVERY BESIDES TWRP.

Hi everyone, i have one dubt in unlock bootloader process...
When phone wipe /data partition???, after or before wait the time to unlock???

Let's remain on topic and avoid bickering.

My bootloader unlocks in 4 days and I am planning to change the room using your guide. I have a doubt, I am a beginner. can I do step 8 with TWRP instead of Pbrb (test3)? Would the steps be the same with the change?

@newbrn of course. Pitch Black is literally a dark themed TWRP with some tweaks.

How To Guide [GUIDE][GSI] Installing LineageOS or GSI ROMs for A127F Binary U7

Hello, today I'll be guiding you to how to install LineageOS or other GSI ROMs on your A127F U7 device.
First, some precaution:
Rich (BB code):
/*
* knox_warranty_void: 0x01
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements:
Code:
* Unlocked bootloader
* Your device's firmware
* Android's platform tools.
* Magisk
* Odin
* U5, U6, U7 TWRP
* GSIs Image for the ROM you want to download
* physwizz's kernel
1) The first step you want to do is, unlock your bootloader. You can simply do that by enabling OEM Unlocking in Developer settings, (Can be unlocked by going to Settings > About Phone > Software Information > tapping "Build Number" 5 times then booting to download mode. (Connect to PC, shutdown your phone, then hold volume up and down buttons, then when you're on the download screen, hold volume up., then press volume up again) WARNING: THIS WILL ERASE YOUR DATA AND PERFORM A FACTORY RESET, SO BACKUP YOUR DATA WHEN NECESSARY.
2) Then, download the firmware you have for your firmware. How? Try visiting sites like samfw and find your firmware by searching A-127F and finding your country's baseband. Then download through your preferred method of downloading. Mine I login to Google, and downloaded through Google Drive, which is faster. (Though it will personally copy the firmware's file to you Google Drive and occupy space on it, so beware of that and delete the file afterwards, the file is in DRIVE > samfw_temporary_folder_dont_delete I assume it's safe to delete after download, so there's that.)
3) Extract the file, and adb push the AP_XXXXX file to your device. How? Download the Android platform tools to the above hyperlink, then extract it, go to the file and then type: e.g adb push [DIRECTORY WHERE YOU EXTRACTED YOUR FIRMWARE FILE]\AP_XXXXXX, [FILL IN THE FILE NAME] /sdcard/
4) Then boot up your device, set it up (minimally), download the magisk from below, (25.1-delta file) then install it. Then from the app, select Install Magisk > Patch from File then select the AP_XXXX file you've extracted from your firmware. Wait, for some minutes, and then see what is the file name.
5) Then pull the file and flash with Odin. (Download below) Use adb pull /sdcard/Download/magisk_patched-XXXX [See the magisk log for the file name] C:\Users\[your user]\Downloads\. Open Odin, select okay, when prompted, select AP, select the magisk_patched-XXXX file you've extracted from your phone, untick auto-reboot, then hit flash.
6) Go to stock recovery, again by pressing Volume Down +Power, then while connected to the PC, press Volume Up + Power then navigate via volume buttons and then press with power button, Wipe data/factory Reset
7) Turn off the phone (while connected to the PC) by pressing Volume Down + Power, then when turned off immediately press Volume Up + Volume Down. Go back to Odin, download the TWRP image below, and put it in AP slot and untick auto reboot. Then flash
8) Boot to recovery, by again Volume Down + Power, when turned off, Volume Up + Power, whilst connected to PC. ( See 6.) Now you've booted to TWRP Recovery. Go to Advance > Terminal then type multidisabler twice. (Very important)
9) Then download the GSI ROM you want to flash, extract it, then adb push it to your /sdcard/, just as you did with 3. (Here is a list of GSI's you can download) (Optional) Either use MTP or adb push to get into your device physwizz's kernel, and GApps (the guide will be in the second post, yet to find a way how to install it)
10) In the recovery, select Install > Install Image > select the GSI ROM's .img file you have, and select System Partition. (Optional) Then select Install Zip Then install physwizz's kernel.
11) Then, reboot, WAILA! There you have it, your own GSI ROM on your A127F U7 device. Enjoy
Credits: @physwizz, for his recovery and kernel ports. Without his hardwork, it wouldn't even be possible to install GSI for U7

How to install GApps.
Method 1 (tested and worked):
Download the A/B Google Apps VNDK Secure variant of Lineage. (In AndyYan's sourceforge page it would be bgS-vndk-secure):
extract the file as usual, and then rename the file as system.img.
Download the attachment below.
adb push both files to your /sdcard/ or any folder you prefer within /sdcard. (Though the files must be in the same directory) i.e. adb push system.img ChonDoe_Flasher.zip /sdcard
Go to TWRP > Install then select the ChonDoe_Flasher.zip,
and WAILA, you have now a working LineageOS with Gapps, it might work with other ROMs too!
Method 2, will post when I have tested it.
Credits: @chondoe for his flasher
--- Theory for flashing twice (disproven, you only need to flash once, here for archive purposes, you don't need to read it if you're not interested):
Go to TWRP > Install then select the ChonDoe_Flasher.zip, TWICE. Do not reboot only doing it once, or else it might bootloop. After flashing once, go back and then do it again. (If you accidentally did it once, tell me if it worked and I'll post the results)
(EXPLAINED: This is a theory of mine, though, I didn't test doing it only once, I'll try to do it once if I ever go back to stock ROM and see if it only requires once, but as of now I tried doing it twice and it worked [the logic behind this is, if you install the .img alone, it will boot-loop due to lack of storage, but the flasher uses e2fsck and resize2fs so along the process, it expands the file system and thereby allowing more space for installation. I theorize doing this once will not work because the script first installs/flash the .img before using e2fsck and resize2fs and therefore still lacks the file system space that it needs to boot, but if you do it twice, you will have already executed the two binaries and thereby allow space for a proper installation of the .img, so it will now boot and not get stuck on an infinite bootloop.])

My phone keeps bootlooping, i followed the tutorial strp by step, can you help me?

MaybeFazat said:
My phone keeps bootlooping, i followed the tutorial strp by step, can you help me?
Click to expand...
Click to collapse
Can you remember what firmware you had? Are you sure it's the right one for your device? Also, this is for A127F U7, make sure your device is compatible. Consequently, what GSI ROM have you flashed? This method only worked with LineageOS 19.1. bvS (by AndyYan). If the bootloop doesn't show the lineage logo, it may be that the GSI file is too big for the system partition, I have yet to found a way to expand our device's /system partition. Try AOSP 12.1 first, or download LineageOS 19.1 bvS from AndyYan's page, and see if it works.

Here https://sourceforge.net/projects/an...20221011-UNOFFICIAL-arm64_bvS.img.xz/download

juliano-oh! said:
Can you remember what firmware you had? Are you sure it's the right one for your device? Also, this is for A127F U7, make sure your device is compatible. Consequently, what GSI ROM have you flashed? This method only worked with LineageOS 19.1. bvS (by AndyYan). If the bootloop doesn't show the lineage logo, it may be that the GSI file is too big for the system partition, I have yet to found a way to expand our device's /system partition. Try AOSP 12.1 first, or download LineageOS 19.1 bvS from AndyYan's page, and see if it works.
Click to expand...
Click to collapse
Alright thanks for the info

Good work

juliano-oh! said:
Can you remember what firmware you had? Are you sure it's the right one for your device? Also, this is for A127F U7, make sure your device is compatible. Consequently, what GSI ROM have you flashed? This method only worked with LineageOS 19.1. bvS (by AndyYan). If the bootloop doesn't show the lineage logo, it may be that the GSI file is too big for the system partition, I have yet to found a way to expand our device's /system partition. Try AOSP 12.1 first, or download LineageOS 19.1 bvS from AndyYan's page, and see if it works.
Click to expand...
Click to collapse
And also, what gapps i need to use?

MaybeFazat said:
And also, what gapps i need to use?
Click to expand...
Click to collapse
That's what I'm currently struggling with, I can't find a GApps that work with any GSI since the /system partition is too small to even install GApps. There are critical and hard to follow tutorials out there that helps with increasing the /system parition but I have yet to try them since it, as I am informed, can hard brick your device. So I'm very cautious about that. @physwizz just recommends installing a ROM with GApps already installed in it (such as Pixel Experience) but I have yet to try that either.

MaybeFazat said:
And also, what gapps i need to use?
Click to expand...
Click to collapse
I accidentally duplicated my reply, sorry

juliano-oh! said:
That's what I'm currently struggling with, I can't find a GApps that work with any GSI since the /system partition is too small to even install GApps. There are critical and hard to follow tutorials out there that helps with increasing the /system parition but I have yet to try them since it, as I am informed, can hard brick your device. So I'm very cautious about that. @physwizz just recommends installing a ROM with GApps already installed in it (such as Pixel Experience) but I have yet to try that either.
Click to expand...
Click to collapse
Can you try magisk gapps?

juliano-oh! said:
Hello, today I'll be guiding you to how to install LineageOS or other GSI ROMs on your A127F U7 device.
First, some precaution:
Rich (BB code):
/*
* knox_warranty_void: 0x01
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements:
Code:
* Unlocked bootloader
* Your device's firmware
* Android's platform tools.
* Magisk
* Odin
* U5, U6, U7 TWRP
* GSIs Image for the ROM you want to download
* physwizz's kernel
1) The first step you want to do is, unlock your bootloader. You can simply do that by enabling
Code:
OEM Unlocking
in Developer settings, (Can be unlocked by going to
Code:
Settings > About Phone > Software Information > tapping "Build Number" 5 times[\CODE] then booting to download mode. (Connect to PC, shutdown your phone, then hold volume up and down buttons, then when you're on the download screen, hold volume up., then press volume up again) WARNING: THIS WILL ERASE YOUR DATA AND PERFORM A FACTORY RESET, SO BACKUP YOUR DATA WHEN NECESSARY.
2) Then, download the firmware you have for your firmware. How? Try visiting sites like samfw and find your firmware by searching [CODE]A-127F
and finding your country's baseband. Then download through your preferred method of downloading. Mine I login to Google, and downloaded through Google Drive, which is faster. (Though it will personally copy the firmware's file to you Google Drive and occupy space on it, so beware of that and delete the file afterwards, the file is in
Code:
DRIVE > samfw_temporary_folder_dont_delete
I assume it's safe to delete after download, so there's that.)
3) Extract the file, and
Code:
adb push
the
Code:
AP_XXXXX
file to your device. How? Download the Android platform tools to the above hyperlink, then extract it, go to the file and then type: e.g
Code:
adb push [DIRECTORY WHERE YOU EXTRACTED YOUR FIRMWARE FILE]\AP_XXXXXX, [FILL IN THE FILE NAME] /sdcard/
4) Then boot up your device, set it up (minimally), download the magisk from below, (25.1-delta file) then install it. Then from the app, select
Code:
Install Magisk > Patch from File
then select the AP_XXXX file you've extracted from your firmware. Wait, for some minutes, and then see what is the file name.
5) Then pull the file and flash with Odin. (Download below) Use
Code:
adb pull /sdcard/Download/magisk_patched-XXXX [See the magisk log for the file name] C:\Users\[your user]\Downloads\
. Open Odin, select okay, when prompted, select AP, select the magisk_patched-XXXX file you've extracted from your phone, untick auto-reboot, then hit flash.
6) Go to stock recovery, again by pressing Volume Down +Power, then while connected to the PC, press Volume Up + Power then navigate via volume buttons and then press with power button,
Code:
Wipe data/factory Reset
7) Turn off the phone (while connected to the PC) by pressing Volume Down + Power, then when turned off immediately press Volume Up + Volume Down. Go back to Odin, download the TWRP image below, and put it in AP slot and untick auto reboot. Then flash
8) Boot to recovery, by again Volume Down + Power, when turned off, Volume Up + Power, whilst connected to PC. ( See 6.) Now you've booted to TWRP Recovery. Go to
Code:
Advance > Terminal
then type
Code:
multidisabler
twice. (Very important)
9) Then download the GSI ROM you want to flash. Here is a list, then
Code:
adb push
then to your /sdcard/, just as you did with 3. (Optional) Either use MTP or
Code:
adb push
to get into your device physwizz's kernel, and GApps (the guide will be in the second post, yet to find a way how to install it)
10) In the recovery, select
Code:
Install > Install Image > select the GSI ROM's .img file you have, and select System Partition.
(Optional) Then select
Code:
Install Zip
Then install physwizz's kernel.
11) Then, reboot, WAILA! There you have it, your own GSI ROM on your A127F U7 device. Enjoy
Credits: @physwizz, for his recovery and kernel ports. Without his hardwork, it wouldn't even be possible to install GSI for U7
Click to expand...
Click to collapse
How it performs? Does it run smoother than OneUI? & Do you have screenshots?

MaybeFazat said:
Can you try magisk gapps?
Click to expand...
Click to collapse
I haven't tried it yet.
MaybeFazat said:
How it performs? Does it run smoother than OneUI? & Do you have screenshots?
Click to expand...
Click to collapse
It performs well, I haven't done any benchmark to see if it performs better than OneUI, but they are pretty different. Although, it performs pretty well in my opinion, and it boots very quickly (as in, the animation only has to run once and it boots already). Unfortunately, I don't have any screenshots, as I reverted back to stock since I need my Google account and Play Store, but you can try and search for "Lineage OS 19. X Screenshots" on Google and I doubt it will give you any different results.

juliano-oh! said:
I haven't tried it yet.
It performs well, I haven't done any benchmark to see if it performs better than OneUI, but they are pretty different. Although, it performs pretty well in my opinion, and it boots very quickly (as in, the animation only has to run once and it boots already). Unfortunately, I don't have any screenshots, as I reverted back to stock since I need my Google account and Play Store, but you can try and search for "Lineage OS 19. X Screenshots" on Google and I doubt it will give you any different results.
Click to expand...
Click to collapse
So i tried for the second time, with Lineage BgS (not BvS since i need gapps) but its bootlooping again, can you help me?

I can't, I tried that too but I haven't found a way to workaround this, sorry to disappoint. I'm guessing that the image is too big for the system that it won't boot. I only find the BvS to be working, and have not yet tried others, except for BgS, which gave me a bootloop too...

it will work for A127F/DSN?

smj320fn-galaxy said:
it will work for A127F/DSN?
Click to expand...
Click to collapse
Yes, but only for LineageOS vanilla, there's yet to find a way to install GApps. If you can live without GApps you can install this then. https://sourceforge.net/projects/an...20221011-UNOFFICIAL-arm64_bvS.img.xz/download

and if i have one ui 4.1 and u7 brinary i still can install it, and in the downloads it says twrp-a127f-u5 brinary?

smj320fn-galaxy said:
and if i have one ui 4.1 and u7 brinary i still can install it, and in the downloads it says twrp-a127f-u5 brinary?
Click to expand...
Click to collapse
yes, the U5 binary TWRP is compatible with U6 and U7

@MaybeFazat I updated the second post. You may now enjoy LineageOS with Gapps. Please tell me what has happened after you install. Feedback will be appreciated.