Database Develop

[GUIDE][ZS620KL][Update 29.08.2019] 5Z How to unlock root up/downgrade and unbrick

Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
[Update 29.08.2019] Added new download locations for raw images
[Update 07.01.2019] Added more current raw image for ZS620KL WW 80.30.96.111
[Update 25.10.2018] Added raw image for ZS621KL.
[Update 09.08.2018] Updated for 80.11.37.95 and future versions.
[Update 20.07.2018] I was able to root FW 80.11.37.86 with Magisk Manager 5.8.3 so you are no longer locked to FW 80.11.37.69 and do not have to downgrade.
This guide is split into two sections: rooting and downgrade/unbrick.
Each section is split into a quick how to for experienced users and a more detailed guide.
General info:
The most current firmware as of 20.07.18 is 80.11.37.86. Newer versions will work too!
This guide is written for firmware 80.11.37.86. If you do not want to upgrade/downgrade to 80.11.37.86 you will need to use the firmware (zip file from ASUS) you are on in all the steps.
If you upgrade your firmware to a newer version AFTER rooting it you will lose root! You will need to patch the boot.img of the new firmware again > follow the rooting guide.
I have only tested this on my ZS620KL Z01RD WW version. It should work on other variants JP/RU.
Magisk hide is working and Safetynet check passes.
Bugs/problems:
Unlocking the bootloader will void your warranty! Currently there is no method known to relock it!
You will get a warning message about your unlocked bootloader at every boot.
You will no longer receive OTA updates but you can download the new firmwares directly from Asus.
You will get a warning message about an internal problem every boot. Which you can disable if you do not need write access to the vendor partition.
> see rooting guide 10.
[Downloads]
for rooting
The latest and official platform tools (adb/fastboot) directly from google.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Payload_dumper to extract the boot.img from the firmware:
https://androidfilehost.com/?fid=818070582850510260
Magisk Manager:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The bootloader unlock app and the 80.11.37.86 firmware for your device (WW/RU/JP) from ASUS:
https://www.asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_Download/
for downgrade/unbrick
raw firmware (ZS620KL WW):
WW 80.10.8.54
https://www.androidfilehost.com/?fid=1899786940962570681
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
WW 80.30.96.111
https://www.androidfilehost.com/?fid=1899786940962570682
https://drive.google.com/file/d/16OgxiPFSDJwhitnqJaITuO-XPOrg_7q9/view
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
Confirmed working by amscova.
raw firmware (ZS621KL):
https://addrom.com/raw-rom-unbrick-for-asus-zenfone-5z-zs621kl/
https://www.androidfilehost.com/?fid=1899786940962570680
https://mega.nz/#F!2fIgmAoa!2q4ra3R1Cp0fyKZDYdVMwg
Confirmed working by B Nath.
[Rooting how to]
Upgrade to firmware 80.11.37.86 and enable usb debugging.
Unlock your bootloader with the app.
Extract boot.img from firmware using payload_dumper.
Patch boot.img with magisk manager.
fastboot flash boot patched_boot.img.
Enjoy root.
[Rooting guide]
You can root any firmware from 80.11.37.86 up with this guide. To upgrade to a newer firmware version copy the zip file (e.g. UL-Z01R-WW-80.11.37.86-user.zip) you downloaded from Asus
to the root of your phones internal memory and reboot or unplug your usb cable.
You will get an update found notification. Start the update. To downgrade check the downgrade guide below.
Enable usb debugging in System > Developer options. If you can not see System > Developer options go to System > About phone > Software information > Build number and tap it multiple times.
This will make the Developer options visible.
WARNING! Upgrading to some firmwares disables usb debugging and you need to enable it again.
Make a backup of all the data you do not want to lose.
Download the platform tools and extract them into a folder (i will use c:\5z\ in this guide) this will create a subfolder platform-tools.
You need a current fastboot version for this to work (due to a/b slots/partitions), so please use the current platformtools!
Download the bootloader unlock app, extract the UnlockTool_9.1.0.3_180621_fulldpi_Draco_GDPR.apk and copy it to your phone.
Use a filemanager on your phone to install it and follow the on screen instructions to unlock the bootloader.
WARNING! You will lose your warranty and all data on the phone so backup beforehand. You will see the first warning message at boot after this. There is currently no method know to relock the bootloader.
Download payload_dumper and extract it to c:\5z\. A payload_dumper-win64 folder will be created.
Download the firmware zip of the version you have on your phone and extract payload.bin from the zip to c:\5z\payload_dumper-win64\payload_input\ folder.
Start c:\5z\payload_dumper-win64\payload_dumper.exe and let it finish. Now copy the c:\5z\payload_dumper-win64\payload_output\boot.img to your phone (i will use the download folder).
Download Magisk Manager, copy the apk to your phone and use a filemanager on your phone to install it. Start the app and update it if you are asked.
When you are asked if you want to install Magisk > install. Select Method > Patch Boot Image File. Now select the boot.img in the download folder and let it finish patching.
Copy the patched_boot.img from the MagiskManager folder on your phone to c:\5z\platform-tools\
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\platform-tools\
To check if your phone has been found:
Code:
fastboot devices
You should see the serial number of your phone.
Now flashing the patched boot image:
Code:
fastboot flash boot patched_boot.img
The output should look something like this:
target reported max download size of 268435456 bytes
sending 'boot' (18724 KB)...
OKAY [ 0.620s]
writing 'boot_a'...
OKAY [ 0.133s]
finished. total time: 0.756s
And the reboot:
Code:
fastboot reboot
Your phone should be booting now and you will see the second warning message "There is an internal problem with your device...".
If you want to get rid of that warning and do not need write access to your vendor partition (you most likely do not):
Open Magisk Manager and in the main screen press Uninstall > Restore Images to restore the images, check Preserve AVB 2.0/dm-verity checkbox in "Advanced Settings" on the main screen, then reinstall Magisk by pressing Install > direct install in the main screen.
Should you be stuck in the Zenfone boot animation or something went wrong, you will need to follow the steps in the unbrick section.
Otherwise your phone is rooted now. Enjoy.
[Downgrade/unbrick how to]
Download and extract the raw firmware.
With the phone in fastboot mode execute flashall_aft.cmd in the extraction folder.
You are now downgraded/unbricked with firmware 80.10.8.54.
Copy firmware version of your choice to internal sd card root and reboot/unplug usb cable to get "update notification".
Start the update to selected firmware from the "update found" notification.
[Downgrade/unbrick guide]
If you need to downgrade the firmware or if you have somehow bricked your device you can try to flash a raw (full) image of the phone.
Download and extract the raw firmware to c:\5z\raw.
If the download link is no longer working google for WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release.zip and download it.
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\raw
To flash the raw image:
Code:
flashall_aft.cmd
This will take a few minutes and the phone will reboot automatically. The first boot will take a little longer but your phone should now be unbricked and downgraded to 80.10.8.54.
You can now go to the root section of the guide and upgrade to a more current firmware.
Thanks to Renaf2 for his ZE620KL guide, GSPD and amscova for providing the ZS620KL raw image links and B Nath for finding the ZS621KL raw image.

Nice Theard
Thank You for your work

Upgrade after rooting
Hello,after downgrade and rooting the phone with your method,it is posible to put in internal memory the last version of firmware(80.11.37.86) and upgrade the phone,or the phone remains blocked in the version of firmware(80.11.37.69) which we make downgrade and root?Thank you for your hard work.

isthisadagger said:
Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
Click to expand...
Click to collapse
Process is too long. I am working on unofficial Unlock Tool so that we can retain the warranty.
For downgrading, there is a tool for that. For me, fastboot codes may mess up the system/cache partitions.
If anyone wanna test my unlocking tool, feel free to PM me via Telegram
MOD EDIT: LINK REMOVED
The distribution of social media links is no longer allowed on XDA. Please refer to the thread linked below:
Telegram and Whatsapp Channels - Going Forward

mihaitaiosub said:
Hello,after downgrade and rooting the phone with your method,it is posible to put in internal memory the last version of firmware(80.11.37.86) and upgrade the phone,or the phone remains blocked in the version of firmware(80.11.37.69) which we make downgrade and root?Thank you for your hard work.
Click to expand...
Click to collapse
Yes it is possible but you will lose root.
Patching the boot.img for 80.11.37.79 and 80.11.37.86 does not seem to work with this method.

isthisadagger said:
Yes it is possible but you will lose root.
Patching the boot.img for 80.11.37.79 and 80.11.37.86 does not seem to work with this method.
Click to expand...
Click to collapse
And is not possible to root again whith method described on this thread?

mihaitaiosub said:
And is not possible to root again whith method described on this thread?
Click to expand...
Click to collapse
This is why we need TWRP.

mihaitaiosub said:
And is not possible to root again whith method described on this thread?
Click to expand...
Click to collapse
It is possible with Magisk Manager 5.8.3.

isthisadagger said:
Warning - USE THIS GUIDE AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICE.
[Update 20.07.2018] I was able to root FW 80.11.37.86 with Magisk Manager 5.8.3 so you are no longer locked to FW 80.11.37.69 and do not have to downgrade.
This guide is split into two sections: rooting and downgrade/unbrick.
Each section is split into a quick how to for experienced users and a more detailed guide.
General info:
The most current firmware as iof 20.07.18 is 80.11.37.86.
I have only tested this on my ZS620KL Z01RD WW version. It should work on other variants JP/RU.
This guide is written for firmware 80.11.37.86. If you do not want to upgrade to 80.11.37.86 you will need to use the firmware you are on in all the steps.
Magisk hide is working and Safetynet check passes.
Bugs/problems:
Unlocking the bootloader will void your warranty!
You will get a warning message about your unlocked bootloader at every boot.
You will get a warning message about an internal problem every boot. Which you can disable if you do not need write access to the vendor partition.
> see rooting guide 10.
[Downloads]
for rooting
The latest and official platform tools (adb/fastboot) directly from google.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Payload_dumper to extract the boot.img from the firmware:
https://androidfilehost.com/?fid=818070582850510260
Magisk Manager:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
The bootloader unlock app and the 80.11.37.86 firmware for your device (WW/RU/JP) from ASUS:
https://www.asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_Download/
for downgrade/unbrick
raw firmware:
https://drive.google.com/file/d/1ogbQeeNDRPFCb9jl3kpRDK_DmsneQ0xL/view?usp=drivesdk
[Rooting how to]
Upgrade to firmware 80.11.37.86 and enable usb debugging.
Unlock your bootloader with the app.
Extract boot.img from firmware using payload_dumper.
Patch boot.img with magisk manager.
fastboot flash boot patched_boot.img.
Enjoy root.
[Rooting guide]
You can root any firmware up to 80.11.37.86 with this guide. To upgrade to a newer firmware version copy the zip file (e.g. UL-Z01R-WW-80.11.37.86-user.zip) you downloaded from Asus
to the root of your phones internal memory and reboot or unplug your usb cable.
You will get an update found notification. Start the update. To downgrade check the downgrade guide below.
Enable usb debugging in System > Developer options. If you can not see System > Developer options go to System > About phone > Software information > Build number and tap it multiple times.
This will make the Developer options visible.
WARNING! Upgrading to some firmwares disables usb debugging and you need to enable it again.
Make a backup of all the data you do not want to lose.
Download the platform tools and extract them into a folder (i will use c:\5z\ in this guide) this will create a subfolder platform-tools.
You need a current fastboot version for this to work (due to a/b slots/partitions), so please use the current platformtools!
Download the bootloader unlock app, extract the UnlockTool_9.1.0.3_180621_fulldpi_Draco_GDPR.apk and copy it to your phone.
Use a filemanager on your phone to install it and follow the on screen instructions to unlock the bootloader.
WARNING! You will lose your warranty and all data on the phone so backup beforehand. You will see the first warning message at boot after this.
Download payload_dumper and extract it to c:\5z\. A payload_dumper-win64 folder will be created.
Download the firmware zip of the version you have on your phone and extract payload.bin from the zip to c:\5z\payload_dumper-win64\payload_input\ folder.
Start c:\5z\payload_dumper-win64\payload_dumper.exe and let it finish. Now copy the c:\5z\payload_dumper-win64\payload_output\boot.img to your phone (i will use the download folder).
Download Magisk Manager, copy the apk to your phone and use a filemanager on your phone to install it. Start the app and update it if you are asked.
When you are asked if you want to install Magisk > install. Select Method > Patch Boot Image File. Now select the boot.img in the download folder and let it finish patching.
Copy the patched_boot.img from the MagiskManager folder on your phone to c:\5z\platform-tools\
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\platform-tools\
To check if your phone has been found:
Code:
fastboot devices
You should see the serial number of your phone.
Now flashing the patched boot image:
Code:
fastboot flash boot patched_boot.img
The output should look something like this:
target reported max download size of 268435456 bytes
sending 'boot' (18724 KB)...
OKAY [ 0.620s]
writing 'boot_a'...
OKAY [ 0.133s]
finished. total time: 0.756s
And the reboot:
Code:
fastboot reboot
Your phone should be booting now and you will see the second warning message "There is an internal problem with your device...".
If you want to get rid of that warning and do not need write access to your vendor partition (you most likely do not):
Open Magisk Manager and in the main screen press Uninstall > Restore Images to restore the images, check Preserve AVB 2.0/dm-verity checkbox in "Advanced Settings" on the main screen, then reinstall Magisk by pressing Install > direct install in the main screen.
Should you be stuck in the Zenfone boot animation or something went wrong, you will need to follow the steps in the unbrick section.
Otherwise your phone is rooted now. Enjoy.
[Downgrade/unbrick how to]
Download and extract the raw firmware.
With the phone in fastboot mode execute flashall_aft.cmd in the extraction folder.
You are now downgraded/unbricked with firmware 80.10.8.54.
Copy firmware version of your choice to internal sd card root and reboot/unplug usb cable to get "update notification".
Start the update to selected firmware from the "update found" notification.
[Downgrade/unbrick guide]
If you need to downgrade the firmware or if you have somehow bricked your device you can try to flash a raw (full) image of the phone.
Download and extract the raw firmware to c:\5z\raw.
If the download link is no longer working google for WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release.zip and download it.
Start your phone in fastboot mode. To do that press and hold "power+volume up" to switch it on until you see the fastboot menu. If you are having trouble getting there,
it helps to release the power button first then the volume up when you see the menu.
Now connect the phone to your computer with the original usb cable. Open a command line with admin privileges and excute the following commands:
To switch to the fastboot dir:
Code:
cd c:\5z\raw
To flash the raw image:
Code:
patchall_aft.cmd
This will take a few minutes and the phone will reboot automatically. The first boot will take a little longer but your phone should now be unbricked and downgraded to 80.10.8.54.
You can now go to the root section of the guide and upgrade to a more current firmware.
Thanks to Renaf2 for his ZE620KL guide and GSPD for providing the raw image name.
Click to expand...
Click to collapse
Does unbricking lock the bootloader back since we will be flashing a raw a file.

With Magisk Manager 5.8.3 the whole guide works like a charm
THX

My Zenfone 5z isn't being detected in fastboot mode, kindly help with correct driver softwares, my PC is running on Windows 10
Update : I got my phone to detect in fastboot

How to wipe cache partition
Hi,
I am able to boot into recovery on Z5z but not able to see "wipe cache partition" option. I only see a wipe data/factory reset option.
I want to wipe cache to see if battery life improves. Can anyone let me know how to do this?
Thanks

chandru.biradar2 said:
Does unbricking lock the bootloader back since we will be flashing a raw a file.
Click to expand...
Click to collapse
No.

kelly66 said:
Hi,
I am able to boot into recovery on Z5z but not able to see "wipe cache partition" option. I only see a wipe data/factory reset option.
I want to wipe cache to see if battery life improves. Can anyone let me know how to do this?
Thanks
Click to expand...
Click to collapse
Honestly killing the cache rarely helps things.

hi guys how to do this on Macbook pro? Any clues?

shantanudl said:
hi guys how to do this on Macbook pro? Any clues?
Click to expand...
Click to collapse
I do not have any experience with mac os but if you want to root:
Adb/fastboot is available for mac os. All you need to do is find a tool to extract the boot.img from the payload.bin.
If you want to downgrade/unbrick: You would need to convert the bat/cmd files in the full firmware to some shell scripts and exchange the fastboot.exe.

How do I un-root, re-lock bootloader?

ferez said:
How do I un-root, re-lock bootloader?
Click to expand...
Click to collapse
unroot: You press "uninstall" in magisk manager or install an updated firmware without patching boot.img or downgrade.
I have not tried re-locking the bootloader.

So if I'm getting this right, after unlocking the bootloader I will not get OTA updates.
But I will be able to download the latest version (SKU) from Asus and put it in /sdcard/ folder, and rebooting will start the update of the new firmware.
Is this correct?
Kind regards
/Jens

jens13 said:
So if I'm getting this right, after unlocking the bootloader I will not get OTA updates.
But I will be able to download the latest version (SKU) from Asus and put it in /sdcard/ folder, and rebooting will start the update of the new firmware.
Is this correct?
Kind regards
/Jens
Click to expand...
Click to collapse
You won't get OTAs + your warranty is voided (due to unlocking Officially)
Yes, you can update your phone by sideloading the zip from ASUS Support Website

[GUIDE] Redmi 6 Pro Root Guide

Disclaimer
Code:
#include <std/disclaimer.h> /* * 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 rooting your device * before doing 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. */
Downloads
Instructions
Unlock your bootloader if you haven't already. Detailed steps can be found here.
Download the ADB and fastboot tools, TWRP Recovery IMG file and Magisk zip from the link above.
Extract the ADB zip into a folder and copy the recovery file into the same folder as well.
Copy the Magisk zip file into your phone's internal storage.
Rename the recovery file to recovery.
In the ADB folder and click on the MFA32 to open a command prompt window.
Connect your phone to your PC and go to the Developer Options previously enabled. Find the USB Debugging option and enable it.
Now hold the Volume + Power Down buttons that will allow the phone to boot into Fastboot mode.
In the fastboot mode, type: fastboot devices.
If your device is detected, great. If not, check your connections, USB Debugging or see if proper device drivers are installed or not.
Next, type: fastboot flash recovery recovery.img. This will flash the recovery in a few seconds.
Next, type: fastboot reboot recovery. As a result, you are welcomed by the recovery screen.
Here, click on Install. Find the previously downloaded Magisk zip and select it to flash. This will flash the required binaries.
Reboot.
Open Play Store and install the Magisk Manager. This will allow you to take proper advantage of your root by using multiple modules with many features.
Enjoy!
Full Guide can be found here - http://xboard.in/redmi-6-pro-recovery-root/.

twrp recovery not reading internal storage.
Hi,
I have a Redmi 6 Pro Indian version with unlocked Boot-loader, MIUI Global 10.2 stable. Flashed twrp recovery (Sakura) successfully but booting into the recovery mode I find it cann't read internal memory (showing 0 MB) and I can't flash necessary files through it for rooting my device.
On rooting into twrp recovery mode, first asks for password for un-encription and when I provide device unlock password, after sometime, it shows password failed.
On tapping 'cancel' option, goes to home of twrp with no option to flash from internal storage since it is 0MB.
Fastboot getvar anti command shows nothing [ anti: (blank)]. Fastboot getvar all shows Rollback ver 2.
Please help.

@Aloke17 Your data are encrypted. You have to do format data. Notice that your internal memory will be erased. Make a backup before.

mar.ur said:
@Aloke17 Your data are encrypted. You have to do format data. Notice that your internal memory will be erased. Make a backup before.
Click to expand...
Click to collapse
It did not work. Have already done that with same result. Can you tell me if I can flash from external storage like otg pendrive etc.?

Aloke17 said:
It did not work. Have already done that with same result. Can you tell me if I can flash from external storage like otg pendrive etc.?
Click to expand...
Click to collapse
I think you did a wipe data, not format. Look at the picture below

mar.ur said:
I think you did a wipe data, not format. Look at the picture below
Click to expand...
Click to collapse
I know difference. Formatted data, not wiped. got same result.

Aloke17 said:
I know difference. Formatted data, not wiped. got same result.
Click to expand...
Click to collapse
Restart again to twrp after format

This is what I did (make sure the TWRP.img and lazy flasher zip (attached) are in the same directory as the adb folder):
1. Put phone to fastboot mode.
2. Run ADB command fastboot boot twrp.img (the twrp image downloaded). Phone will reboot into TWRP. It will ask for password to decrypt, just hit back and ignore it for now.
3. Go to Wipe, Format Data. Swipe to Factory Reset. Advanced Wipe: Dalvik/ ART Cache, Cache, System, Internal Storage.
4. Go to Mount and mount System.
5. Run ADB command adb push twrp.img /sdcard
6. Go to Install, Install Image, select the TWRP.img file that you just pushed and flash it as recovery but don't reboot yet.
7. Run ADB command adb push lazyflasher-no-verity-opt-encrypt.zip /sdcard
8. Go to Install, Install Zip, select the zip file that you just pushed.
9. Go to Reboot. Power Off.
10. Boot the Device into TWRP Recovery (press volume up + power button).
Hope this helps a noob like me who wasn't able to flash TWRP due to strange errors.
PS: Bootloader was unlocked and device was running MIUI 10.2.2 Stable (Chinese ROM). I switched to Revenge OS (from XDA) based on Android Pie after this.

Can anyone please tell me how to get rid of SAKURA anti rollback. I'm currently on miui rom global beta 9.6.27..????
I waana flash xiaomi.eu rom on my phone.
I bricked my phone while flashing EU rom direct through twrp.

I followed this guide and it worked. The good thing about this guide is you can mess up and then get the mobile back to working state. I copied from a blog but can not post the link as i have fewer than 10 posts.
The contents of the blog in case if its deleted
1. unlock bootloader.
1.1 To unlock bootloader linking your mobile number to the device is mandatory to unlock bootloader. Read my rant[1] at the end of this post during the flashing as it takes some time. For now move to step 2 after unlocking the bootloader
2. check if the bootloader is unlocked by running the command "fastboot oem device-info"
3. flash the system image.
3.1 Download the image from the mi.com site sakura_india_global_images_V10.3.2.0.PDMMIXM_20190527.0000.00_9.0_global_0aaaa35167.tgz # md5sum 0aaaa35167e8edd299f0dd9418f04c62
3.2 untar
3.3 cd sakura_india_global_images_V10.3.2.0.PDMMIXM_20190527.0000.00_9.0_global/
# poweroff mobile, press volume down + poweron to go to fastboot mode
3.4 ./flash_all.sh
4 twrp flashing using boot and not flash because flashing to recovery parition is successfull but the recovery boot does not launch twrp so use the temporary method(flashboot boot)
4.1 fastboot boot twrp-3.2.3-0-sakura.img # md5sum 16759dcc425042d6a63b635f777a7690
4.2 twrp -> advanced settings ->sideload -> check both the cache to wipe -> swipe
4.3 adb sideload Magisk-v19.4.zip # md5sum 2a1def27607601ecaa780ee4b15210c2
4.4 flashing lazyflasher went in to loading forever, so skip that. it works without lazy flashing
5. reboot will boot to system and then download the MagiskManager apk from its website
5.1 enable the developer options for adb to transfer the MagiskManager apk to mobile
5.2 adb push MagiskManager-v7.3.4.apk /sdcard # md5sum 16e9ad8767665234dea7896a4137288e
5.3 on the mobile install the apk
6. to test it
6.1 adb shell
6.2 su
6.3 the above command should pop up requesting for permissions for root.
[1] Rant on Xiaomi's lies on embracing developer culture
TLDR: Xiaomi don't lie about embracing the hacker ethic. Accept you are evil with some lame excuse that is much more respectable.
It is very evil of Xiaomi to make the user provide their mobile number(thats right, you must provide your **working** sim card number) to unlock the bootloader. They will not unlock if your sim is not active, you must enable internet on your sim, link the sim number to mi account and only then they will unlock the bootloader. If you just use wifi it is not supported and yet they lie on their faq that the need sim for data usage.
Here is the faq they do not say about the sim card requirement . I have archived it in case after reading this Xiaomi might change this faq
The Following is the Q&A of faq
> Isn't locking bootloader against Mi's 'geek' spirit?
> Locking bootloader is aimed to provide a better user experience, which we've been trying to do the whole time. In the meantime, we've provided an unlocking tool for senior users who know their ways around flashing and tweaking their devices.
> The unlocking procedure will need Internet access to get the unlocking password. Also, the Mi Account logged in on the Mi phone and the unlocking tool needs to be the same. Otherwise, the unlocking request will be denied. This will ensure that ill-intentioned people will not get access to your personal data.
Atleast the moto company wanted just the device id to unlock bootloader.
I was rooting for Xiaomi a long back when i saw their faq where the question was "Can i root my mi mobile " and the answer was something along the lines of "Of coures you can, what do you think of us . we embrace hacker ethic. Now i can not find a link to this faq. Is someone find this please comment the link, i will add here.
Hope this guide helps some one.

grv29a said:
Can anyone please tell me how to get rid of SAKURA anti rollback. I'm currently on miui rom global beta 9.6.27..????
I waana flash xiaomi.eu rom on my phone.
I bricked my phone while flashing EU rom direct through twrp.
Click to expand...
Click to collapse
Just try to unlock bootloader as i did.
After flashing, is there any 'unlock' under Mi Logo? If no, need to unlock again.

[GUIDE] All about unlocking bootloader, TWRP and rooting Redmi Note 8/8T

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.
* 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.
*/
A guide to unlock bootloader, flash a custom recovery and root your Redmi Note 8/8T device :
1. UNLOCKING BOOTLOADER :
Backup your data first. Unlocking will erase your data.
- Enable Developer Options in your phone by tapping the "MIUI Version" 7 times in About Phone.
- Go to Settings > Additional Settings > Developer Options.
- Enable OEM Unlocking, USB Debugging and USB Debugging (Security Settings) .
- Also add account in Mi Unlock Status (Can be found in Developer Options).
- Install the required ADB and Fastboot drivers in your PC from here.
- Download Mi Unlock to PC from here, and sign in with your Mi Account.
- Shut down your phone manually, and hold volume down key and power button to enter Fastboot mode.
- Connect your phone to PC using USB cable and click "Unlock" in Mi Unlock Tool.
- You will be given a specific time (168 hours usually).
- Wait for the given time. Make sure to use your phone and don't log out of your mi account from the phone or reset your device.
- Once waiting time is over, redo Unlock process.
- Your phone will be unlocked successfully.
2. FLASHING TWRP :
- Install the required ADB and Fastboot drivers in your PC if not already in step 1. from here.
- Download TWRP from here.
- Put that TWRP in the ADB and Fastboot installed folder (mostly C:\Program Files (x86)\Minimal ADB and Fastboot).
- Rename that recovery(TWRP file) to "recovery" for convenience (optional).
- Click on Start Menu, type cmd
- Right click and select Run as administrator
- Then type:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
- Now Connect your phone to PC With USB Debugging on (keep phone on).
- Type:
Code:
adb devices
and accept the pop up on phone's screen.
- Now reboot your phone to Fastboot mode either manually by shutting down phone and then holding volume down key and power button or by:
Code:
adb reboot bootloader
- Once in Fastboot mode type:
Code:
fastboot devices
- Your device ID will be visible on Screen.
- Then type(hit ENTER after each line):
Code:
fastboot flash recovery recovery.img
fastboot boot recovery.img
- Now your phone will boot into TWRP.
OPTIONAL STEPS (Not Recommended): Encryption is always recommended for better security. However if you don't want encryption in your device, follow these steps. Again, not recommended.
- In TWRP go to Wipe and select Format Data(don't go to advanced). Type yes and format data. [This process will format all your data so make sure your data is backed up]
- Go back to TWRP home and Reboot > Recovery.(Don't reboot system or else you will have to repeat whole process again).
- Done
3. ROOTING :
- Download Magisk zip to PC from here.
- Download Universal DM-Verity and ForceEncrypt disabler from here. (Only required if you followed optional steps.)
- When in TWRP transfer the file(s) to phone and go to Install.
- Here select Magisk zip file and swipe to flash.
- Then select Universal DM-Verity and ForceEncrypt disabler zip and swipe to flash(Make sure to flash this at last or else phone won't boot). (Only required if you followed optional steps.)
- Reboot system.
- Done. Debloat. Enjoy
Links
1. Minimal ADB and Fastboot
2. MI Unlock Tool
3. TWRP
4. Magisk
5. Universal DM-Verity and ForceEncrypt Disabler (OPTIONAL)
If this helped you then hit the Thanks Button. Good Luck.

Thanks for guide. Anyway, latest versions of Windows 10 don't have "Open command prompt here" option. Instead, they have PowerShell. I don't know how PowerShell will react with ADB, so, for these Windows 10 is better to:
Click on Start Menu, type cmd
Right click with mouse and choose "Run as administrator"
Type these commands (hit ENTER after each line):
cd\
cd "program files (x86)
cd "minimal adb and fastboot"
Now the user is on right folder.
--------------------------------
A question: I'm on stock ROM and have a Google Apps account on my phone, and I'm currently using stock Second Space feature to handle it. As encryption is mandatory to use a Google Apps account, I can't use "disable encryption". Or will Second Space be encrypted even if "main account" isn't? There are any problems to use Magisk with encrypted phone?

romulocarlos said:
Thanks for guide. Anyway, latest versions of Windows 10 don't have "Open command prompt here" option. Instead, they have PowerShell. I don't know how PowerShell will react with ADB, so, for these Windows 10 is better to:
Click on Start Menu, type cmd
Right click with mouse and choose "Run as administrator"
Type these commands (hit ENTER after each line):
cd\
cd "program files (x86)
cd "minimal adb and fastboot"
Now the user is on right folder.
--------------------------------
A question: I'm on stock ROM and have a Google Apps account on my phone, and I'm currently using stock Second Space feature to handle it. As encryption is mandatory to use a Google Apps account, I can't use "disable encryption". Or will Second Space be encrypted even if "main account" isn't? There are any problems to use Magisk with encrypted phone?
Click to expand...
Click to collapse
totally forgot about the powershell thing . Thanks to you I updated my post.
What do you mean by Google Apps account. Do you mean google account??. I'm using a decrypted phone right now and google apps work just fine with decryption too.
There aren't any problems to use Magisk with encrypted phone(I used it myself for a good week or so before decrypting).
Unfortunately as of now I don't have the answer to your second space question. Will let you know once I get it myself.

the_weird_aquarian said:
totally forgot about the powershell thing . Thanks to you I updated my post.
What do you mean by Google Apps account. Do you mean google account??. I'm using a decrypted phone right now and google apps work just fine with decryption too.
There aren't any problems to use Magisk with encrypted phone(I used it myself for a good week or so before decrypting).
Unfortunately as of now I don't have the answer to your second space question. Will let you know once I get it myself.
Click to expand...
Click to collapse
You must update the command to change folder on cmd. Put the path in quotes, or else the users will receive an error!
Code:
cd "C:\Program Files (x86)\Minimal ADB and Fastboot"
About Google Apps, is also called Google for Work, or Work Profile. Is MANDATORY to have the phone encrypted, or the account won't sync.
Thank you for feedback!

romulocarlos said:
You must update the command to change folder on cmd. Put the path in quotes, or else the users will receive an error!
Code:
cd "C:\Program Files (x86)\Minimal ADB and Fastboot"
About Google Apps, is also called Google for Work, or Work Profile. Is MANDATORY to have the phone encrypted, or the account won't sync.
Thank you for feedback!
Click to expand...
Click to collapse
the command works fine without quotes too man, checked it myself. both ADB and Fastboot commands work fine.
I'll check about Google for work issue. :good:

the_weird_aquarian said:
the command works fine without quotes too man, checked it myself. both ADB and Fastboot commands work fine.
I'll check about Google for work issue. :good:
Click to expand...
Click to collapse
You're right. Tested right now and worked. Maybe newer Win10 versions are "smarter" than older... who knows...
Well, about the second space, thanks, but you don't need to check with an Google Apps account.
If your phone is decrypted, just open Second Space, configuring it for first time use as you like. Then, on Second Space, go Settings -> Password and security -> privacy. Check if encryption is active.
Thanks again!

Thank you for this awesome tutorial.. now i m in "waiting mode" for unlocking bootloader ?
Just one dummy question for me sir .. can i root my device while i am using stock rom (miui 11 global) ? Or i have to install custom rom ? Thank you ?

Mozar3lla said:
Thank you for this awesome tutorial.. now i m in "waiting mode" for unlocking bootloader
Just one dummy question for me sir .. can i root my device while i am using stock rom (miui 11 global) ? Or i have to install custom rom ? Thank you
Click to expand...
Click to collapse
Yes you can root on stock rom. Rooting is not rom specific. You can root on any rom.
Hope it helps.

@the_weird_aquarian thanks for the tutorial mate, do i have to flash dm verity everytime i flash magisk????
and also I found this tutorial and software for flashing twrp, is it ok to use this software too?
https://github.com/XiaomiWiki/XiaomiWiki.github.io/blob/master/wiki/Flash_TWRP_and_custom_ROMs.md

shayanb2004 said:
@the_weird_aquarian thanks for the tutorial mate, do i have to flash dm verity everytime i flash magisk????
and also I found this tutorial and software for flashing twrp, is it ok to use this software too?
https://github.com/XiaomiWiki/XiaomiWiki.github.io/blob/master/wiki/Flash_TWRP_and_custom_ROMs.md
Click to expand...
Click to collapse
dm-verity is just required to stop the stock mi recovery from coming back. Hence it's just for MIUI based roms. However disable forceencrypt helps you get rid of force encryption of miui or other custom roms(so that you can access internal storage from recovery too if you are flashing something). The zip provided has both features in one file. Just rename the file to whatever you want to disable(see instructions here).
Regarding that tool on github, I have never used it personally as I like doing each step myself so if something goes wrong I know the last working step and from there I can figure out what went wrong. Using the tool might or might not work for you. Use at your own risk.

the_weird_aquarian said:
dm-verity is just required to stop the stock mi recovery from coming back. Hence it's just for MIUI based roms. However disable forceencrypt helps you get rid of force encryption of miui or other custom roms(so that you can access internal storage from recovery too if you are flashing something). The zip provided has both features in one file. Just rename the file to whatever you want to disable(see instructions here).
Regarding that tool on github, I have never used it personally as I like doing each step myself so if something goes wrong I know the last working step and from there I can figure out what went wrong. Using the tool might or might not work for you. Use at your own risk.
Click to expand...
Click to collapse
Thanks for the info mate
damn I have to wait a whole week to unlock my bootlaoder

shayanb2004 said:
Thanks for the info mate
damn I have to wait a whole week to unlock my bootlaoder
Click to expand...
Click to collapse
Yeah you gotta wait for a week. Weird Xiaomi policy. Can't help you with that though.

the_weird_aquarian said:
Yeah you gotta wait for a week. Weird Xiaomi policy. Can't help you with that though.
Click to expand...
Click to collapse
yea too bad... I cant use it for a week cuz all of my data is gonna get wiped again
I need to transfer all my data and apps from my old phone with migrate
so I will wait

shayanb2004 said:
yea too bad... I cant use it for a week cuz all of my data is gonna get wiped again
I need to transfer all my data and apps from my old phone with migrate
so I will wait
Click to expand...
Click to collapse
Make sure to atleast keep your phone turned on.

I will try it to root my device to get rid off the annoying ads. But my ordered cell phone does not come yet and I still patient to wait it.
Question :
1. Can I use the Mi Mover application to migrate data from an old cellphone (Redmi Note 5) to Redmi Note 8?
2. Whether migrating data (via Mi Mover) before root or do data migration after root ? Because my old RN5 already rooted, have it TWRP and Magisk too.

AMJ_Vario said:
I will try it to root my device to get rid off the annoying ads. But my ordered cell phone does not come yet and I still patient to wait it.
Question :
1. Can I use the Mi Mover application to migrate data from an old cellphone (Redmi Note 5) to Redmi Note 8?
2. Whether migrating data (via Mi Mover) before root or do data migration after root ? Because my old RN5 already rooted, have it TWRP and Magisk too.
Click to expand...
Click to collapse
I suggest you to move AFTER you root your new device, because to have root, you must unlock the bootloader. And when you unlock the bootloader, all data is lost.

romulocarlos said:
I suggest you to move AFTER you root your new device, because to have root, you must unlock the bootloader. And when you unlock the bootloader, all data is lost.
Click to expand...
Click to collapse
So its mean, first the device RN8 must do unlock the bootloader, then root it, next is migration data from old cellphone.
Is that the right way?
Is the migration data from old cellphone, will included the third party application from that old cellphone too? Is it will compatible on RN8?
Or just migration important data only (like email account + Mi account + contact + notes, etc) and the application 3rd party should be installed one by one on the RN8 exacly as RN5?
Sorry for asked to much becuse I dont want to make a mistake on the new devices.
Just guide me into the right way, please..
Thanks for the respond..:good:

AMJ_Vario said:
So its mean, first the device RN8 must do unlock the bootloader, then root it, next is migration data from old cellphone.
Is that the right way?
Is the migration data from old cellphone, will included the third party application from that old cellphone too? Is it will compatible on RN8?
Or just migration important data only (like email account + Mi account + contact + notes, etc) and the application 3rd party should be installed one by one on the RN8 exacly as RN5?
Sorry for asked to much becuse I dont want to make a mistake on the new devices.
Just guide me into the right way, please..
Thanks for the respond..:good:
Click to expand...
Click to collapse
In fact, I never used Mi Mover. As each device has its features, I prefer to install apps one by one. My data is on cloud, so for me is easyer.
I suggest you to do the transfer, only for tests, just after you receive your phone. These videos may help you also:
https://www.youtube.com/watch?v=shf-i8z86Ms and https://www.youtube.com/watch?v=ql-f88qllrE

@the_weird_aquarian mate have you tested orangefox recovery?
I'm hearing a lot about it, but donno anything :S
thinking if it is good instead of twrp or not?

shayanb2004 said:
@the_weird_aquarian mate have you tested orangefox recovery?
I'm hearing a lot about it, but donno anything :S
thinking if it is good instead of twrp or not?
Click to expand...
Click to collapse
yes so I have recently flashed orangefox about 2 weeks ago or something. I personally don't use anything other than official twrp, but I flashed orangefox because of it's miui OTA update feature. You can flash if you are planning on staying on stock rom with a decrypted device, as I have dirty flashed stock rom with my decrypted device but it always ends up in bootloop with official twrp. I have to format data everytime. Surprisingly Orangefox solves this issue. Also if you are a fan of theming then it provides a few custom fonts, colors and themes. However if your device is encrypted there's absolutely no reason to switch from official to any other recovery unless you want to customize the looks of your recovery.

[GUIDE] How to unlock bootloader in the Moto E6 Plus + Install TWRP, with Windows and Linux

Hello guys, in this guide I will tell you how to unlock the bootloader of the Moto E6 Plus.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
DISCLAIMER:
Code:
/*
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this system image 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.
*
*/
What we will do first is a downgrade to version 76 of firmware since the new versions it's not allowed unlock bootloader, for this we will use SP Flash Tool v5.1916 (since the most current version does not give an error) and later we will flash some files for complete the unlock bootloader besides that we will install TWRP to install some GSI since the stock system it cannot be used.
This process is for 32/2 and 64/4 variant.
Links of download at the end of the post.
WARNING: THIS PROCESS ERASES ALL USER DATA AND VOIDS THE WARRANTY IN ADDITION THAT THE SYSTEM STOCK CANNOT BE USED.
Spoiler: PROCESS OF THE UNLOCK WITH WINDOWS
Prerequisites:
A computer with Windows (bruh)
ADB and Fastboot installed
Have installed the device drivers to be detected in fastboot mode.
Have downloaded the lk, vbmeta and recovery files.
Have downloader SP Flashtool and the ROM to downgrade.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
Once the necessary files have been downloaded the process is the following"
Unpack the SP Flash Tool and open "flash_tool.exe" file.
Once opened the app they will have to press up to the right the section "Options" and select "Option", when i open them they have to uncheck the second option.
Then close the window and in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
fastboot flashing unlock_critical
And press Volume + in the phone to unlock the bootlaoder and DO NOT reboot still
Spoiler: If you logged into the system directly
In case of having started in the system without installing the files, you will have to start in the recovery mode and do a factory format.
After that you can flash the files from fastboot.
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
fastboot flash lk lk.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img
Now restart in recovery and go to Wipe > System > Advanced options > Resize.
Without this it would appear that there is 8GB of memory instead of 32/64.​​Now it only remains to flash the GSI.​
​
Spoiler: PROCESS OF THE UNLOCK WITH LINUX
Prerequisites:
A computer with Linux (bruh)
ADB and Fastboot installed
Have downloaded the lk, vbmeta and recovery files.
Have downloader SP Flashtool and the ROM to downgrade.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
Once the necessary files have been downloaded the process is the following
Unpack the SP Flash Tool, and mark as to executable "flash_tool" file and open as superuser, if you don't know the commands are the following:
Code:
sudo chmod +x flash_tool
sudo ./flash_tool
Now in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
sudo fastboot flashing unlock_critical
And press Volume + in the phone to unlock bootloader and DO NOT reboot still.
Spoiler: If you logged into the system directly
In case of having started in the system without installing the files, you will have to start in the recovery mode and do a factory format.
After that you can flash the files from fastboot.
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
sudo fastboot flash lk lk.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash recovery twrp.img
Now restart in recovery and go to Wipe > System > Advanced options > Resize.
Without this it would appear that there is 8GB of memory instead of 32/64.​​Now it only remains to flash the GSI.​
​If you don't know which GSI to try first, I recommend one from Phhusson, Ermitain or Andy.
NOTE: The system will be encrypted, and in this build of TWRP the encryption is not support so the files of internal storage will appear with numbers and letters random, if you want to remove the encryption flash the dm-verity.
NOTE 2: After unlocking the bootloader you can update the firmware to the latest version, but you will have to flash the lk and vbmeta files again (besides of recovery).
NOTE 3: The GSI architectures for each variant are: A64 AB for 32/2 and ARM64 AB for 64/4.
NOTE 4: If you are going to flash a GSI with GApps you will first have to flash a vanilla Phhusson GSI and start in it, after that you have to flash the GSI with GApps WITHOUT wipes and you can use it normally
Links of download:
ROM to downgrade : https://mirrors.lolinet.com/firmware/moto/pokerp/official/RETLA/ (the one that says in the name 32B its for 32/2 variant and the one that says in the name 64B its for 64/4 variant, bruh)
SP Flashtool: https://spflashtool.com/download/ (download the 5.1916 version)
ADB and Fastboot (Windows only): https://androiddatahost.com/uq6us
lk, vbmeta and TWRP files: https://drive.google.com/drive/folders/19wDFLDOoFTIDO-sv3vxWJ-CUEG1Q3sl-?usp=sharing
Credits:
@eluallen to do the first guide of how to unlock the bootloader and vbmeta file.
@Siddk for the recovery.
@LichtEstarossx for lk file and give some development to pokerp ;-;.

Fastoh said:
Hello guys, in this guide I will tell you how to unlock the bootloader of the Moto E6 Plus
DISCLAIMER:
Code:
/*
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this system image 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.
*
*/
What we will do first is a downgrade to version 76 of firmware since the new versions it's not allowed unlock bootloader, for this we will use SP Flash Tool v5.1916 (since the most current version does not give an error) and later we will flash some files for complete the unlock bootloader besides that we will install TWRP to install some GSI since the stock system it cannot be used.
This process is for 32/2 and 64/4 variant.
WARNING: THIS PROCESS ERASES ALL USER DATA AND VOIDS THE WARRANTY IN ADDITION THAT THE SYSTEM STOCK CANNOT BE USED.
Spoiler: PROCESS OF THE UNLOCK IN WINDOWS
Once the necessary files have been downloaded the process is the following"
Unpack the SP Flash Tool and open "flash_tool.exe" file.
Once opened the app they will have to press up to the right the section "Options" and select "Option", when i open them they have to uncheck the second option.
Then close the window and in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
fastboot flashing unlock_critical
And press Volume + in the phone to unlock the bootlaoder and DO NOT reboot still
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
fastboot flash lk lk.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img
Now reboot to recovery and flash some GSI
If you don't know which try first with the GSI of Phhusson or Lineage of Andy
Spoiler: PROCESS OF THE UNLOCK IN LINUX
Once the necessary files have been downloaded the process is the following
Unpack the SP Flash Tool, and mark as to executable "flash_tool" file and open as superuser, if you don't know the commands are the following:
Code:
sudo chmod +x flash_tool
sudo ./flash_tool
Now in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
sudo fastboot flashing unlock_critical
And press Volume + in the phone to unlock bootloader and DO NOT reboot still
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
sudo fastboot flash lk lk.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash recovery twrp.img
Now reboot to recovery and flash some GSI.
if you don't know which try first with the GSI of Phhusson or Lineage of Andy
NOTE: The system will be encrypted, if you want to remove the encryption flash the dm-verity.
NOTE 2: After unlocking the bootloader you can update the firmware to the latest version, but you will have to flash the lk and vbmeta files again (besides of recovery).
Links of download:
ROM to downgrade : https://mirrors.lolinet.com/firmware/moto/pokerp/official/RETLA/ (the one that says in the name 32B its for 32/2 variant and the one that says in the name 64B its for 64/4 variant, bruh)
SP Flashtool: https://spflashtool.com/download/ (download the 5.1924 version)
ADB for Windows: https://androiddatahost.com/uq6us
lk, vbmeta and TWRP files: https://drive.google.com/folderview?id=19wDFLDOoFTIDO-sv3vxWJ-CUEG1Q3sl-&usp=sharing
Click to expand...
Click to collapse
I've been looking for GSI-Treble support,
And my system drops this.
So in various posts people say "For this phone we have to install GSI aonly-Arm32"
I don't know what Is The Correct One And I Need Help

ShotRomsS6edge said:
I've been looking for GSI-Treble support,
And my system drops this.
So in various posts people say "For this phone we have to install GSI aonly-Arm32"
I don't know what Is The Correct One And I Need Help
Click to expand...
Click to collapse
Ahí te dice en la imagen, las GSIs compatibles son las que son A64 xd // There it tells you in the image, the compatible GSIs are those that are A64 xd

Dont get it, there is way too many fake websites with USB drivers for ADB and fastboot and none of them are working, ive tried your adb driver aswell but once I get into fastboot windows just says: Android device with a 28 error code which means that there is no driver installed, could you give me the link?
EDIT: adb only works when the device has booted.

simbanono said:
Dont get it, there is way too many fake websites with USB drivers for ADB and fastboot and none of them are working, ive tried your adb driver aswell but once I get into fastboot windows just says: Android device with a 28 error code which means that there is no driver installed, could you give me the link?
EDIT: adb only works when the device has booted.
Click to expand...
Click to collapse
What is missing are the drivers, try to download them from this link (is the link that came in the flash tool zip xd): https://androiddatahost.com/276a2

Fixed already ty

.

somebody know how to unlock bootloader moto e6 play xt2029-1? im trying to unlock bootloader and everthing i try it fails, please help me :c

cyanogenmodricky said:
somebody know how to unlock bootloader moto e6 play xt2029-1? im trying to unlock bootloader and everthing i try it fails, please help me :c
Click to expand...
Click to collapse
mmmmm, maybe downgrading to the oldest firmware version you can find

Fastoh said:
mmmmm, maybe downgrading to the oldest firmware version you can find
Click to expand...
Click to collapse
Well, that is what I have tried to do and spflashtools gives me many problems with this model :c

cyanogenmodricky said:
Well, that is what I have tried to do and spflashtools gives me many problems with this model :c
Click to expand...
Click to collapse
try the version of sp flashtool that uses LMSA
in the log it says which version

Fastoh said:
try the version of sp flashtool that uses LMSA
in the log it says which version
Click to expand...
Click to collapse
ohh ok, i will try it and i tell you if works :3

well i get make downgrade to the lowest version i found, now i can't unlock the bootloader with
fastboot flashing unlock_critical
it gives me "waiting device" :c
edit: i install adb, fastboot and moto drivers, now when i wirte fastboot flashing unlock appears "unknow command"

hey hi,i have a problem, so i did everything as you write it but when i did the flashtool thing it didn't recognize the phone, but it was making contact, i installed a lot of drivers until one of them make it work, so when i did the fastboot thing it wasn't recognize the phone again, what can i do? my phone is the 32/2 version

Alejandro2810 said:
hey hi,i have a problem, so i did everything as you write it but when i did the flashtool thing it didn't recognize the phone, but it was making contact, i installed a lot of drivers until one of them make it work, so when i did the fastboot thing it wasn't recognize the phone again, what can i do? my phone is the 32/2 version
Click to expand...
Click to collapse
what SO do you use? windows or linux? because in windows the fastboot mode did not work either ;-;

Fastoh said:
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Click to expand...
Click to collapse
But... How remove battery if this not removable?..

Mortyk said:
But... How remove battery if this not removable?..
Click to expand...
Click to collapse
what ._.? the moto e6 plus has a removable battery, I think you have the e6s instead of the e6 plus

Fastoh said:
what ._.? the moto e6 plus has a removable battery, I think you have the e6s instead of the e6 plus
Click to expand...
Click to collapse
Yeap i'm have e6s. I thought e6 plus have not removable battery also.
Do you know how to flash e6s?

Mortyk said:
Yeap i'm have e6s. I thought e6 plus have not removable battery also.
Do you know how to flash e6s?
Click to expand...
Click to collapse
mmmm, look first trying with lmsa to have as it tells you to do the firmware re-installation, then do the same steps you did in the LMSA but in the flashtool

If you want to downgrade you have to do it with the firmware of the e6s because if you do it with the e6 plus your phone will have birck.

[12.1][GAPPS] AOSP ANDROID 12.1 for A21s

---
Disclaimer: This will void warranty.
You will need to unlock bootloader.
*All your data will be lost*
---
Info:
Android version 12.1 (12L)
July 2022 patch
Tested on A217F & Dual SIM working
GApps included so you don't have to flash them
Part 1 - Unlocking bootloader:
Skip this if you've already done it.
1. Enable Developer Options, go to OEM Unlocking and turn it on.
2. Plug in phone to PC, restart the phone and right when it turns off, keep holding VOLUME DOWN + VOLUME UP till you see the Download Mode
3. Hold VOLUME UP to enter Bootloader Unlock mode
4. Press VOLUME UP to accept, and let the phone restart and erase
* To check if it worked, head back to Download mode and check if "OEM LOCK" is "OFF"
Part 2 - Flash recovery:
1. Download Odin and recovery U7/recovery U6/recovery U5
2. Put device to Download Mode (Hold VOLUME UP + VOLUME DOWN while plugging in phone to PC)
3. Open Odin and hit AP and select recovery file
4. (optional) go to Options tab and untick Auto Reboot
5. Hit start
* If it fails with error "Only official binaries are allowed to be flashed(recovery)", then boot device up, connect to internet, and then change Date to some time ago like January 5th 2022
Part 3 - Flash the ROM:
1. Download and Extract the ROM
2. Download the kernel
3. Download and Extract platform-tools (ADB and Fastboot)
4. Open up Command Prompt and cd into platform-tools folder
5. Plug in phone to PC, restart or turn off phone and hold VOLUME UP + POWER for about 5 seconds. You should enter Lineage Recovery.
6. Tap Advanced, then Enter Fastboot
7. Type in command prompt "fastboot flash system " and drag the ROM .img file and hit enter. This should take around 3 to 5 minutes.
8. Exit Fastboot mode on the phone and go to Apply Update, Apply from ADB
9. Type in command prompt "adb sideload " and drag the kernel .zip file and hit enter. Press Yes when the phone asks to.
10. Reboot the phone.
Notes:
* DO NOT APPLY A SCREEN LOCK, or else the settings app will crash along with the setup wizard, and if you do it from settings you won't be able to change it, disable it or enable fingerprint unlock
* SuperSU root is pre-installed so you can 'adb sideload ' the UPDATE-unSU.zip from recovery, then 'adb sideload ' the Magisk apk attached below ("app-debug.apk") after renaming it to .zip
Credits:
@physwizz for kernel
Kernel source https://github.com/physwizz?tab=repositories
@phhusson for GSI ROM
Good luck!

Why you don't Look on my thread?

oli231 said:
Why you don't Look on my thread?
Click to expand...
Click to collapse
Hi,
I have tried the GSI you linked in your guide but it just gave me a bootloop similar to many other guides, including the Samsung PixelExperience Android 12.0 GSI further down in the comments. So after I did my own research and tries I put together this guide with the resources I used to make the device work.

RestlessGoose said:
Hi,
I have tried the GSI you linked in your guide but it just gave me a bootloop similar to many other guides, including the Samsung PixelExperience Android 12.0 GSI further down in the comments. So after I did my own research and tries I put together this guide with the resources I used to make the device work.
Click to expand...
Click to collapse
thank you for all the effort made to give us an amazing experience I have a question when can we expect a stable version

I have U8 Binary what should i do about it ?

Does it work on A217M?

how do i fix the fingerprint?

7MODE__TN said:
I have U8 Binary what should i do about it ?
Click to expand...
Click to collapse
mine also u8, i use lineage recovery from youtube. and its work

Hi I did all the steps and it is stuck on boot screen showing Samsung Galaxy A21s.
I used u8 lineage recovery.

Kevonism said:
mine also u8, i use lineage recovery from youtube. and its work
Click to expand...
Click to collapse
Hi is this working for you? Do you have a link to the recovery?

nxs_neo said:
Hi is this working for you? Do you have a link to the recovery?
Click to expand...
Click to collapse
u8 lineage recovery.tar
drive.google.com

Hi, i do all the steps in the tutorial and use the u8 bootloader and recovery that Kevonism has uploaded. But after the install via adb sideload it goes in a bootloop (with kernel flash). Could someone help me out?
My discord is: cristiano#0717

shottiemodder said:
Hi, i do all the steps in the tutorial and use the u8 bootloader and recovery that Kevonism has uploaded. But after the install via adb sideload it goes in a bootloop (with kernel flash). Could someone help me out?
My discord is: cristiano#0717
Click to expand...
Click to collapse
Same for me