Database Info

Ulefone Power 5 twrp + root + project treble

Hello everyone, lets root your ulefone power 5 and if you want: flash another rom. I'm kinda new here so don't mind if I'm telling things in a stupid way.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in 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.
*/
Ok, first of all, massive shout out to @gamr13 and @Dukino and @CarelMinnaar for providing some of the files.
Original threat: https://forum.xda-developers.com/android/help/ulefone-power-5-twrp-root-t3848501/
Link to the website I copied and translated the guide from: https://www.chinahandys.net/android-9-auf-dem-ulefone-power-5-anleitung/
Code:
If you are using any custom rom on your phone, I strongly
recommend reflashing your whole phone with the original
firmware provided by ulefone. I'll add the link.
I assume you know how to flash, otherwise search on youtube or
request it and I'll add a guide.
Most files you may need and worked in my case:
MediaFire
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
More files in the spoiler below.
Let's begin!
First of all, make sure your phone is recognized by your pc and use a good cable. (the original one broke pretty quickly in my case)
Next, go to system and search for 'build number'.
Tap it untill it says: you are now developer.
Go to developer options and enable: OEM unlocking. Then power your phone off.
Next, download the fastboot and adb zip file I provided. If you already use adb and fastboot, download the recovery zip and you know how it works.
Extract the 'android' folder and put it on the root of your system disk (mostly /C).
Next, go to your command prompt and type: cd \android
Now you start your phone in bootloader. Press and hold volume up and power and let your phone cycle untill you enter bootloader.
Select 'fastboot'.
Plug your phone into your pc and type in the command prompt: fastboot devices
Now you should see the serial number of one device (in my case it was something like ABCD1234567890). If not, install some fastboot drivers and use device manager to select the fastboot driver for your phone.
Then, type: fastboot oem-unlock
Select Yes on your phone and let it reboot.
Re-enter fastboot on your phone.
To be sure: fastboot devices
Flash your recovery using: fastboot flash recovery TWRP_3.2.3_Ulefone_Power_5_AND_5S.img
Then, you need (maybe not but just do it) to reboot straight into bootloader. So press volume up and power untill it shows the bootloader, and then select recovery.
Now your phone may be encrypted or something like that. Select 'Wipe' and accept.
Next, put your gsi (A only, arm64), gapps and/or your decrypt file on your sdcard and flash it!
Known bugs:
- VoLTE - I needed to use a simcard from a different provider to get calling working.
- Hotspot
- Seems sticky to 2.4G?
- MTP not working in recovery
- When waking up your device you may encounter some weird behaviour. Just wait a second and it's gone.
Spoiler: The old guide
Files:
https://mega.nz/#!N2hijYAB!0LLshTYgW...SUfOKpV5BELo4A (seems to be down and dated)
or
http://www.mediafire.com/folder/55lxwzgdd938t/ulefone_power_5
or
https://drive.google.com/drive/folders/1totRbNzS1RBeSO66WW2O0hG2kPGbGERl?usp=sharing
So, the method.
1.) In the files above you will find a file ulefone power 5 twrp root. Extract it and find the map called SP_Flash_Tool. Open this and run the flash_tool.exe. Please download the firmware.zip and the flashtool.zip and extract them. Put the decrypt.zip on your sdcard. (in some cases you need also the 'MT65xx_USB_VCOM_DRIVERS.zip' to install properly)
2.) Once opened the flashtool.exe, go into the options menu, click the connection tag and make sure USB is selected. make sure its set to Full speed and auto detect.
3.) Browse through the map sp flashtool and use the MTK_AllInOne_DA.bin file as the DA file (may be selected by default).
4.) Select the scatter file found in the firmware folder with all the .img files. Its called: MT6763_Android_scatter.txt
5.) While unplugged, hold the volume up and power button to load the phone into it's bootloader mode.
(if your phone is bricked in any screen skip this step) Turn your phone totally off.
6.) Set the SP flash tool to download only and press the download button to start the download.
7.) Plug your phone in and as expected, nothing will happen.
8.) Now, hold the volume up and power button continuously. Keep holding it until the SP Flash tool starts start downloading and the bottom bar loads things. Be sure you immediately loose the buttons, otherwise it soft-bricks itself so you have to start the download again.
9.) Be patient and wait until you get the green check mark, then unplug your phone.
10.) Boot directly back into bootloader. (vol. up and power, hold it untill you get the fastboot screen. Sometimes it takes up to 4 reboots), select and boot recovery.
11.) Now it's all for you! Put something on your sdcard and flash it. Mine seems to be broken so I used an usb stick, wich is working fine. MTP is not working in the recovery.
12.) CarelMinnaar published the new decrypt file, wich I thrust more than the previous russian one. Put it on your sdcard, do a full wipe and install. This should ban the forced encryption.
12.)
A.) For root: flash the magisk .zip file from the files above or search on the internet for the right one.
Thanks to @gamr13
1. Reboot to TWRP
2. MAKE A FULL BACKUP (every partition checked)
3. Mount System and Vendor
4. Go back to the main screen
5. Advanced > File Manager
6. Go to Vendor
7. Go to the "lib" folder
8. tap libdirect-coredump.so and Copy File
9. Go to /system/lib
10. paste the file in here
11. Go to /vendor/lib64
12. Copy libdirect-coredump.so
13. Paste in /system/lib64
14. Install Magisk
15. Reboot
16. Go to Magisk > Download > Search for "SafetyPatch" by hackintosh5
17. Reboot and enjoy
Click to expand...
Click to collapse
B.) 1. For another rom: search overhere for a system.img Download the A only variant. I'll keep you updated below. I am not using this phone frequently anymore, so updates may come later. @gamr13 will keep you updated
2. Wipe cache, dalvik cache, data and System.
3. Select flash .img and flash the .img at your System.
4. Flash magisk or other mods.
5. There may be some bugs. Sms was not working on the phh treble for me. The launcher crashed also.
13.) Boot up
14.) Enjoy! Feel free to ask anything.
Got some pm's asking what to do if stuck on boot/recovery, this video explains the return to stock process. In short: start spflashtool, select the scatter file in the stock firmware, select download only, firmware upgrade or download and format. Plug your cable in. Then click start, and press vol. up and power until you hear the 'new device found' sound on your pc and let it go. Then just reboot.
Feel free to use his files or mine. Doesn't really matter.

Working gsi images
These gsi images are tested on this phone:
Android 8.1
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
bugs: sometimes the screen flickers when powering on. (once or twice per month)
Android 9
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
bugs: a bit laggy. It takes up to 30 seconds to wake up from just screen off. Maybe a bug with the sleep state. When you use your phone frequently you don't suffer from this.
Thanks to @gamr13 :
Alright boys, yet another stride made today.
I've done some extensive testing on some Generic System Images for the Ulefone Power 5. This GSI seems to be the most stable I've used so far and best of all, it has root built-in (of course, it's LineageOS).
This is the only one I've gotten to work with ViPER4Android and root. Quick note that this still does have the screen flicker on the lock screen, but it's not as bad in this ROM compared to others I've tried.
Android Q GSIs currently do not work on the Ulefone Power 5, I've tried and fought hard with 'em but nothing. So, Pie it is for now.
Note: Magisk DOES NOT work. Please do not flash it on this ROM or you will break root access and need to reflash the system image.
First things first:
https://sourceforge.net/projects/andyyan-gsi/files/
1) Download the A-ONLY ROM.(avN): https://sourceforge.net/projects/an...309-UNOFFICIAL-treble_arm_avN.img.xz/download
2) Make a backup of your stock ROM as it is, just in case in TWRP.
3) WIPE System, Data, Cache and Dalvic in the Advanced Wipe section of TWRP.
4) Flash the image as a System Image in TWRP.
5) Flash Open Gapps
7) Reboot into ROM
8) Enable Developer Options and enable root for apps and adb
9) Download ViPER4Android 2.5.0.4 (This is critical as the newest release will not work)
10) Install the driver
11) On every reboot you will have to go into V4A and go to Settings > Turn on developer mode > Disable SELinux
12) Enjoy Android Pie with ViPER4Android on your Ulefone Power 5.
Click to expand...
Click to collapse
Android 11
Havoc os
[11][OFFICIAL] Havoc-OS 4.1 [ARM64/ARM/A64][A/AB/AB-VNDKLITE][GApps/Vanilla]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com
Not the quickest, but looks nice with the pixel inspired interface. No extra bugs found.

Handy thread!
I can’t get Magisk working though on any GSIs. I don’t ever get a prompt to allow root access to an app or even with it set to automatically grant, nothing happens and apps don’t detect it, yet, Magisk is installed and Magisk Modules install and work no problem.
Weird issue.

oes20 said:
These gsi images are tested on this phone:
Android 8.1
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
bugs: sometimes the screen flickers when powering on. (once or twice per month)
Android 9
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
bugs: a bit laggy. It takes up to 30 seconds to wake up from just screen off. Maybe a bug with the sleep state. When you use your phone frequently you don't suffer from this.
Click to expand...
Click to collapse
Does Magisk work for you on these GSIs?

gamr13 said:
Does Magisk work for you on these GSIs?
Click to expand...
Click to collapse
It works on (i guess) the android 8 gsi. I do not recommend magisk, as it messes with your /vendor partition. That partition can not be factory reset other than re-flashing the whole recovery/system/vendor/radio etc. Magisk is also not optimized for this device. Tweaks like viper4androidfx won't work. I don't use my phone anymore at this moment, so any tips, tricks or new information is always welcome to ensure that everybody can get the same good experience

oes20 said:
It works on (i guess) the android 8 gsi. I do not recommend magisk, as it messes with your /vendor partition. That partition can not be factory reset other than re-flashing the whole recovery/system/vendor/radio etc. Magisk is also not optimized for this device. Tweaks like viper4androidfx won't work. I don't use my phone anymore at this moment, so any tips, tricks or new information is always welcome to ensure that everybody can get the same good experience
Click to expand...
Click to collapse
That reply gave me serious doubt that you know a single thing about what you're doing. If it touches /vendor, you flash stock vendor.img in fastboot mode, ez pz. Not that it matters at all since nothing will get messed up at all. Magisk works perfectly fine on stock ROM. V4A works on stock, but when I use any GSI then no apps that require root work at all.

gamr13 said:
Handy thread!
I can’t get Magisk working though on any GSIs. I don’t ever get a prompt to allow root access to an app or even with it set to automatically grant, nothing happens and apps don’t detect it, yet, Magisk is installed and Magisk Modules install and work no problem.
Weird issue.
Click to expand...
Click to collapse
It is a problem, I know. We can't do anything than reporting these problems to the Magisk team and hope for help. In my case, Magisk worked for root, but not for the modules. I got also knocked out of Snapchat because of Magisk. Just one of those little things that are part of our development hobby

gamr13 said:
That reply gave me serious doubt that you know a single thing about what you're doing. If it touches /vendor, you flash stock vendor.img in fastboot mode, ez pz. Not that it matters at all since nothing will get messed up at all. Magisk works perfectly fine on stock ROM. V4A works on stock, but when I use any GSI then no apps that require root work at all.
Click to expand...
Click to collapse
In my case I got root acces working in Magisk. I apologize for that part about the vendor. You are right about that. I am trying my best to share my experience. I am no expert in anything.

Alright boys, yet another stride made today.
I've done some extensive testing on some Generic System Images for the Ulefone Power 5. This GSI seems to be the most stable I've used so far and best of all, it has root built-in (of course, it's LineageOS).
This is the only one I've gotten to work with ViPER4Android and root. Quick note that this still does have the screen flicker on the lock screen, but it's not as bad in this ROM compared to others I've tried.
Android Q GSIs currently do not work on the Ulefone Power 5, I've tried and fought hard with 'em but nothing. So, Pie it is for now.
Note: Magisk DOES NOT work. Please do not flash it on this ROM or you will break root access and need to reflash the system image.
First things first:
https://sourceforge.net/projects/andyyan-gsi/files/
1) Download the A-ONLY ROM.(avN): https://sourceforge.net/projects/an...7-UNOFFICIAL-treble_arm64_avN.img.xz/download
2) Make a backup of your stock ROM as it is, just in case in TWRP.
3) WIPE System, Data, Cache and Dalvic in the Advanced Wipe section of TWRP.
4) Flash the image as a System Image in TWRP.
5) Flash Open Gapps
7) Reboot into ROM
8) Enable Developer Options and enable root for apps and adb
9) Download ViPER4Android 2.5.0.4 (This is critical as the newest release will not work)
10) Install the driver
11) On every reboot you will have to go into V4A and go to Settings > Turn on developer mode > Disable SELinux
12) Enjoy Android Pie with ViPER4Android on your Ulefone Power 5.

Android 10 and TWRP...
Me. I tested 10 different roms of Android 10 and none works correctly .. I always stay on the Android logo that lights up in a loop. if you find information and manipulations or roms that work and are stable, send me the link or download. Thank you. And if you also find a new TWRP custom 3.3.0 or 3.3.1, put the download here. Thanks ?

gamr13 said:
Alright boys, yet another stride made today.
I've done some extensive testing on some Generic System Images for the Ulefone Power 5. This GSI seems to be the most stable I've used so far and best of all, it has root built-in (of course, it's LineageOS).
This is the only one I've gotten to work with ViPER4Android and root. Quick note that this still does have the screen flicker on the lock screen, but it's not as bad in this ROM compared to others I've tried.
Android Q GSIs currently do not work on the Ulefone Power 5, I've tried and fought hard with 'em but nothing. So, Pie it is for now.
Note: Magisk DOES NOT work. Please do not flash it on this ROM or you will break root access and need to reflash the system image.
First things first:
https://sourceforge.net/projects/andyyan-gsi/files/
1) Download the A-ONLY ROM.(avN): https://sourceforge.net/projects/an...7-UNOFFICIAL-treble_arm64_avN.img.xz/download
2) Make a backup of your stock ROM as it is, just in case in TWRP.
3) WIPE System, Data, Cache and Dalvic in the Advanced Wipe section of TWRP.
4) Flash the image as a System Image in TWRP.
5) Flash Open Gapps
7) Reboot into ROM
8) Enable Developer Options and enable root for apps and adb
9) Download ViPER4Android 2.5.0.4 (This is critical as the newest release will not work)
10) Install the driver
11) On every reboot you will have to go into V4A and go to Settings > Turn on developer mode > Disable SELinux
12) Enjoy Android Pie with ViPER4Android on your Ulefone Power 5.
Click to expand...
Click to collapse
8 Days later and I can confirm the ROM has been really stable with no issues other than the lock screen flicker which rarely happens, especially compared to other ROMs. Battery life has had a significant increase even when putting the phone under heavy usage (Call of Duty: Mobile and other games). Performance has shown a decent increase compared to the stock ROM. All in all, very impressed with the substantial improvements the GSI has brought over the stock Oreo firmware that came with this phone.

Can not install ANDROID 10 AOSP v201 !
Hello, I tested all versions of Android 10 phhusson and none works ..
phhusson offers to do this manually but I do not understand where to put it and how to run it!
phhusson: "need to manually setprop ro.skia.ignore_swizzle true"
If you have a solution to my problem, tell me here because I'm tired of Android 9 .. I'd like to upgrade to the latest version and not bother with this Android 9 .. Thanks ​

Android 10 GSIs currently do not work with the Ulefone Power 5.

gamr13 said:
8 Days later and I can confirm the ROM has been really stable with no issues other than the lock screen flicker which rarely happens, especially compared to other ROMs. Battery life has had a significant increase even when putting the phone under heavy usage (Call of Duty: Mobile and other games). Performance has shown a decent increase compared to the stock ROM. All in all, very impressed with the substantial improvements the GSI has brought over the stock Oreo firmware that came with this phone.
Click to expand...
Click to collapse
Tried to install the .xz gsi-image in TWRP but that doesn't work. Can anybody tell me how to install this image, because in TWRP you can only choose between .zip and .img install. Thanks in advance!

fernseher said:
Tried to install the .xz gsi-image in TWRP but that doesn't work. Can anybody tell me how to install this image, because in TWRP you can only choose between .zip and .img install. Thanks in advance!
Click to expand...
Click to collapse
You have to extract the file and then you will have an .img
Extract it with Winrar or 7ZIP

PetroChina said:
You have to extract the file and then you will have an .img
Extract it with Winrar or 7ZIP
Click to expand...
Click to collapse
This!

A guy was able to install Android 10 with another TWRP
I will soon receive the recovery on Facebook,
I am impatient for me and for all of you who tries to
install Android 10 without success, I hope to have it this week!
I'll let you know about Ulefone Power_5's friends <3
https://1drv.ms/u/s!AidaoCKFpLudgeJAwtAZTJlaLIV2EQ?e=6N3RaD​

PetroChina said:
I will soon receive the recovery on Facebook,
I am impatient for me and for all of you who tries to
install Android 10 without success, I hope to have it this week!
I'll let you know about Ulefone Power_5's friends <3
https://1drv.ms/u/s!AidaoCKFpLudgeJAwtAZTJlaLIV2EQ?e=6N3RaD​
Click to expand...
Click to collapse
Great! Let us know what bugs it has (if any) and especially for TWRP if it has the screen flicker!

gamr13 said:
Great! Let us know what bugs it has (if any) and especially for TWRP if it has the screen flicker!
Click to expand...
Click to collapse
I will tell you everything, I must first test it personally and after the upload on Mediafire.
In my opinion, I hope that the scienceillements of the TWRP will not be there ​

I have the files but I can not install it because it did not explain very well the steps ..
http://www.mediafire.com/file/eqzhwznxxr9qlsf/TWRP_3.3.1_UlefoneP5.img/file
http://www.mediafire.com/file/1sf9mi9qlcv5ari/no_encryption_mod.zip/file
He told me this and I do not understand much and it is not clear enough... : no encryption mod first before install latest twrp if your phone doesnt boot from old twrp to twrp 3.3.1​

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

[Stock ROM][Combination][RMM state solution][GUIDE AIO] and many more for M30s

What's currently included in this thread :-
TWRP (With/without magisk)
Installing EdXposed
Root with magisk (not recommended due to bootloops, use twrp with magisk)
RMM state Prenormal solution
Stock and combination firmware and Kernal source Gdrive links
Tools for flashing and downloading latest firmware
Post 2
Hide bootloader unlocked warning message
DeGoogle & debloat M30s and install MicroG
Enable Haptic feedback on m30s (or any other samsung phone)
BACKUP YOUR EFS PARTITION BEFORE DOING ANYTHING​If EFSpartition is corrupted or lost, you would not be able to get calls and wifi and your IMEI will be permanently lost.
There is currently no way of restoring corrupted EFS partition since it is device specific, so flashing stock firmware will also be useless
Here is one guide. follow this or any other that works for you.
Here is another (droid view.com/restore-efs-imei-galaxy-s7/)
OR You can Backup all partitions using twrp (nandroid backup) and store in someplace safe (make sure to tick all partitions including EFS)
This is an excellent guide regarding EFS (thanks to @PlayingPoise). I HIGHLY RECOMMEND READING IT BEFORE PROCEEDING.
TWRP (With/without magisk) (huge thanks to @santhoosh)
Thread
there are two .tar files, flash the one you need
Pro Tip: I would recommend Smalipatcher module to reboot directly into magisk system.
Installing EdXposed
See This for installation video OR This Or This for installation guide.
This, for official website
And This for github!
NOTE: v0.4.6.0_beta from github requires custom magisk otherwise the system wont boot since github hosts alpha versions, so i advice to follow the video tutorial since it has installed the most stable EdXposed
Rooting with Magisk (Currently causing random bootloops since custom Kernal is req., i recommend flashing twrp with magisk)
From magisk official repo and This Link, Both are same, but i just wanted to make AIO thread)
thanks to @santhoosh and @topjohnwu
Unlocking Bootloader
Normally I wouldn’t provide instructions for this, but since things had changed drastically from previous Samsung devices, and there are some caveats, I figure this would be helpful.
* Allow bootloader unlocking in Developer options → OEM unlocking
* Reboot your device to download mode. Either use adb reboot download, or use turn off m30s, press vol+ and vol- simultaneously (while powered off) and connect to pc.
* Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Just when you think the bootloader is unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will reject any unofficial partitions before VaultKeeper explicitly allows it.
* Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to internet in the setup!
* Enable developer options, and confirm that the OEM unlocking option exists and grayed out! The VaultKeeper service will unleash the bootloader after it confirms that the user has the OEM unlocking option enabled.
* if there is no OEM unlock option, set phone's date to 7+ days and back and now see.
* Your bootloader now accepts unofficial images in download mode.
Instructions
* Download the firmware for your device.
* Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
* Install the latest Magisk Manager
* In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
* Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
* Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
* Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options!
* Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
* We now want to boot into the stock recovery to factory reset our device.
* Full data wipe is mandatory! Do not skip this step.
* Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the Vol up and power to boot to recovery . Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
* Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
* This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
* The device will automatically reboot for the first time it boots. This is completely normal and done by design.
* After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
* You shall see Magisk Manager in your app drawer; if not, manually install the APK you downloaded in step 3 and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
* Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Voila! Enjoy Magisk
Additional Info
* Magisk actually patches 3 partitions on your device:
vbmeta: replace with empty vbmeta image to disable partition verification
boot: remove the signature of the image to prevent soft bricks
recovery: this is where Magisk is actually installed
* Never, ever try to restore either of the 3 images mentioned back to stock! You can easily brick your device by doing so, and the only way out is to do full Odin restore following with factory reset. Just don’t do it.
* If you want to upgrade your device, never flash the stock AP tar file with the reasons mentioned above. Always pre-patch the firmware before flashing in Odin.
* If you don’t need to patch the full firmware, you can manually create a tar file with at least vbmeta.img, boot.img, and recovery.img to let Magisk Manager patch your images in the proper way.
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
1. Powering up normally → System without Magisk
2. Power + Volume Up → Bootloader warning → Release all buttons → System with Magisk
3. Power + Volume Up → Bootloader warning → Keep holding volume up → Actual recovery
I would recommend Smalipatcher module to reboot directly into magisk system.
Updates: For each and every updates, either magisk or system update always patch the firmware with magisk and flash using odin(data will not be wiped if HOME_CSC
used instead of CSC)
RMM state Prenormal solution
Flash stock firmware
Boot up WITH sim inserted, CONNECT to internet during setup (or you can connect after setting up, but perform below operations only when connected to internet).
Enable developer options and go to them.
Now connect to internet and go to dev options, now set date 8 days back and check dev options for OEM unlocking
if it's still not there set date to today and again 8 days back and again check.
This worked for me and OEM unlocking was there and RMM state was changed to checking.
(what we are doing is fooling phone to believe that sim was inserted for more than 7 days)
Stock and combination firmware and Kernal source
Below are Gdrive links for Combination firmware for (M307FXXU1ASH9) and (M307FXXU2ASK2) and ROM M307FXXU1ASHI, M307FXXU2ASL2, M307FXXS2ATB3 (FOR INS ONLY, for other regions, use frija or samfirm).
I have also uploaded Kernal source for M307FXXU2ASL2 on gdrive for faster download.
Tools included
The following tools are also included in the shared folder, they are up to date as of FEB 2020, but i have attached links to original threads of xda to give credits and in case they are updated, you can download them from there. (As i said, this is AIO thread to find tools, none of them are my creation)
Frija, Samfirm continued and Samfirm are Tools for downloading Official firmware from samsung servers with high speed (so no to sammobile and other ****ty premium websites)
Frija thanks to @invmini, Github
SamFirm thanks to @zxz0O0, Github
SamFirm_continued, Github
Odin
Patched Odin by @realbbb
Frija not working ? install both vcredist_x00 for your device !
(check your windows settings to know which version to install)
(Microsoft Visual C++ 2010 Redistributable Package) and (Microsoft Visual C++ 2008 Redistributable Package)
https://www.microsoft.com/en-US/download/details.aspx?id=29 (x86) 2008
https://www.microsoft.com/en-US/download/details.aspx?id=5555 (x86) 2010
https://www.microsoft.com/en-US/download/details.aspx?id=15336 (64bit) 2008
https://www.microsoft.com/en-US/download/details.aspx?id=14632 (64bit) 2010
-Open Frija and type in your model (mine is SM-m307f) and your CSC : (mine is INS).
(All models on samfrew: https://samfrew.com/model/SM-M307F/).
Thanks to @BK
Other Tools
PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer
Samsung firmware naming convention and explanation (Outdated)
SM-M307F - Galaxy M30s Samfrew
Extract Samsung PIT File from Samsung Firmware -> www.droid views.com/extract-samsung-pit-file-from-firmware (remove space b/w "droid" and "views")
NAND Erase Samsung Devices in Odin -> www.droid views.com/nand-erase-odin-samsung-firmware (remove space b/w "droid" and "views")
Latest Odin Downloader: https://odindownloader.com/category/download
Samsung USB Driver: https://samsungusbdriver.com/category/download
Samsung Firmware: https://firmwarefile.com/category/samsung
Links​LINK (Pm me if link is dead. If there is error like "try after some time", make a copy of file to your drive and then download)

Hide bootloader unlocked warning message
See Here
DeGoogle & debloat M30s and install MicroG
Here
Enable Haptic feedback on m30s (or any other samsung phone) (thanks to ak****)
1- download "Settings database Editor" from playstore.
2- scroll to bottom and find "haptic_feedback_enabled" and change it to 1

Just in case

great, im planning to buy this device and sell my a70, wouldn't have though a little bit of my thread would have been used there also combination files cannot be flashed anymore until a fix is found (nope Z3X Samsung tool don't work )

BK said:
great, im planning to buy this device and sell my a70, wouldn't have though a little bit of my thread would have been used there also combination files cannot be flashed anymore until a fix is found (nope Z3X Samsung tool don't work )
Click to expand...
Click to collapse
Are you talking about the frija and samfirm part?
I think i took it from some other thread which i cant find now. (maybe s10 or note10 ones)
Edit: Gave credits to you

How to flash Combination firmware?
I am trying to flash combination firmware [COMBINATION_FAC_FA90_M307FXXU1ASH9_FAC_CL16672589_QB25543275_REV00] with Odin v3.13.3B Patched but it doesn't work, giving this error on the phone
"Please get the approval to use factory binaries (PIT)"
Anyone know any way to make it work? It would be really nice to be able to downgrade to U1 binaries.

nobody_nowhere said:
I am trying to flash combination firmware [COMBINATION_FAC_FA90_M307FXXU1ASH9_FAC_CL16672589_QB25543275_REV00] with Odin v3.13.3B Patched but it doesn't work, giving this error on the phone
"Please get the approval to use factory binaries (PIT)"
Anyone know any way to make it work? It would be really nice to be able to downgrade to U1 binaries.
Click to expand...
Click to collapse
it's currently impossible to install a test/debugging firmware without a samsung dev account that work as an authorization to flash combination files.

Sm-m307f/ds
Hi i got OTG update and my phone didnt restart after that, i have been trying to find the right Stock firmware for my Samsung M30S SM-m307F/DS but i couldnt find the right one, can you please help me out with the link of the right firmware for my phone.
Thanks

Watch this video broo...you will get to know how to download all latest updated frimware

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

Can someone help me to understand this custom ROM installation?

Hello, I'm new here, I've been dealing with certain ROM mods for a little while. My test device is an old Samsung Galaxy S4 mini (GTI9195). Now I've been sitting for a few days trying to figure out how to bring my device up to date as best as possible. Lineage OS seemed the best to me. Unfortunately there is no officially confirmed software for my device directly from Lineage, which is why I looked elsewhere. I came across this thread on XDA: https://forum.xda-developers.com/t/...520-r890-unofficial-11-0-0-lineageos-18-1-for -s4-mini.4189967/ . The user arco68 is, so to speak, the boss among S4 mini modifications. Unfortunately, I can't find exact instructions anywhere (especially for the recovery) on how to install all the packages correctly. That's why I researched. I was able to record various steps, but cannot determine if they are correct. Can someone on this forum please help me? My steps:
1. Turn on developer options
2. Turn off OEM encryption (if available)
3. USB debugging on.
4. Download and install Android platform tools in Path
5. Download and zip Magisc
7. Put the phone in bootloader/fastboot/download mode (volume down + home)
8. Flash Team Win Recovery Project (or other custom recovery).
9. Restart phone and boot into recovery mode (volume up + home + power)
10. Erase all data
11. Copy Google Apps to Phone (Optional)
12. Copy Lineage OS (or other custom rom) to phone
13. Install packages one by one (OS first)
14. Reboot device
15. Wait and set up

Okay, First of all requirement-
A portable sd card- Because after flashing twrp, you might face issue where you can't access internal storage from twrp. That's because the phone might be encrypted. You have to decrypt it by flashing a "disable dm verity- forceencrypt.zip". In this case, you might not be able to transfer files from pc when booted into twrp. So, It's a smart move to insert a sd card containing all required files before to avoid these problems.
Another requirement is samsung drivers installed in pc. I will attach that file.
Follow these steps -
1/Unlock bootloader -Go to developer options. Turn on oem unlocking. It will tell you that you're going to loss all data. Proceed. If it doesn’t tell you anything, then there is definitely some extra process to unlock bootloader of your device.(search on internet)
2/Download your phone's official firmware in pc- it will help you if anything goes wrong. Search " Sm fw" on google. Go to first site. Create an account. Search the model number, Download a firmware that matches with all your device's information in "About phone".
3/ Download the lineageos rom and twrp recovery for your model. Then install device info hw from play store to check bits(32/64). Search open gapps. Go to the website. "arm" is for 32 bit & "arm64" is for 64 bit. Select which matches to your device’s bit. Then select the android version of the custom rom. Then select "Pico". Download the file. Next, download latest magisk 25.2 from github page. Rename the apk file to "magisk.zip" Move rom,gapps, magisk.zip to SD CARD. Keep twrp in pc.
4/In pc, download latest odin software. It's an special software for samsung download mode. (There is no fastboot mode in samsung)
5/Boot your device into download mode. And connect with pc.
6/In pc, extract the twrp file(If It's in zip format). Open odin software, Go to options, turn off auto reboot. Now select "AP" & select that extracted twrp file. Click open. Then hit start button.
(Note that most of the samsung devices can't boot stock rom after flashing twrp. So you have to flash custom rom to boot your device. Follow the next step)
7/Boot into twrp wipe>format data>type "yes". Press home button. Install>Select storage>SD card>select the rom.zip. Then add more zips> select the gapps.zip. Again, add more zips> select magisk.zip. After all, swipe to flash.
After installation, reboot device.
What if anything goes wrong?
Extract the stock firmware that you downloaded from sm fw. Connect device in download mode. Open odin, select AP,BL,CP,CSC file one by one. Start flashing. You device will be alive again.