Database Develop

[Guide][TWRP 3.1] How to Flash TWRP 3.1 on Lenovo ZUK Z2 Pro

The recoveries I post are and tested for Lenovo Z2 Zuk Z2 Pro ONLY!
Requirements:
Unlocked phone bootloader
and your phone booted in fastboot mode, otherwise it will not work.
Recovery.img is the same recovery found on Lenovo forums (link below)
Download from MEGA
Mega
Images are in thumbnails, click on them to enlarge
Short guide:
1) Simply extract the zip
2) Open cmd.exe and cd to the directory you extracted
3) Put your phone in fastboot mode by shutting down your phone, if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
4) Paste the following commands:
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
You should get the same results I got:
Long guide for newbies with Windows 10 [the same might be for Windows 7/8]:
1) Download the zip I have uploaded and extract it to a folder with your favorite archive manager [I use WinRAR] and open it
2) Hold Shift and Right Click on empty space in the folder
3) Left click on Open command window here or open command prompt here
4) Put your phone in fastboot mode by shutting down your phone, power it on and if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
5) Paste the following commands by copying one line each time
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
Contents of Uploaded RAR/Zip Archive:
adb.exe & fastboot.exe taken from adb-setup-1.4.3 zip/rar file, which was found on Google, don't have a source link
drivers where taken from ZUK_UsbDriver_1.0.6 zip/rar from a guide which was found on google, don't have a source link
recovery images where taken from the sources below
Sources & Thanks:
Recovery 3.0.8 was taken from:
https://forum.xda-developers.com/le...t/twrp-recovery-zuk-z2-standard-pro-t3415395/
credits go to @raimondomartire
Recovery 3.1 was found on official Lenovo Forums:
http://bbs.lenovomobile.cn/z2pro/t508552/
Google translated Lenovo Forum Page:
https://translate.google.com/transl...n&u=http://bbs.lenovomobile.cn/z2pro/t508552/
Q&A:
Q: I do the same steps you did, in command prompt after pasting your commands I get the following: "< waiting for device >
or I wait for long periods of time or I get a [ERROR] message
A: Chances are 100%, you have the wrong drivers or not drivers installed, most devices use their own drivers for fastboot mode or adb/fastboot commands
If you have a Lenovo Zuk Z2 Pro like me, your device needs to be identified as "ShenQi Composite ADB Interface" in device manager.
Not "Android" or "Android ADB Interface" and because of that fastboot does not identify your device at all
Q: Why do you use 2 commands (fastboot flash and fastboot flash) instead of one?
A: I am not 100% sure but I think fastboot flash recovery, flashes the recovery image you have selected [permanently, until you flash a different one] in your device and you can boot into it anytime you want without using a PC
and the second boots your phone with the recovery image but does not flash it, meaning you keep the stock or the one you have flashed in the past.
So I use the first commmand to permanently flash the recovery and the second to boot the phone in recovery mode without using any phone button combinations to boot into, saves me the time and hassle.
Q: Why use Chinese Custom Recovery instead of an English one?
A: This recovery has Chinese and English Language support. However, if you go to the translated google forum link which I have posted below, the thread's title is: Z2 pro Brush] [zuk z2Pro] Twrp Recovery 3.10 update, support Andrews 7.0 7.1 7.1.2ROM
So I think, Recoveries need to also support the custom ROMS you want to flash, also it is taken from official lenovo forums and chances are they have added more features and fixes.
For example using 3.0.8 recovery I couldn't install LineageOS 14.1 custom rom, I was getting Error 7 when I was trying to flash
Q: I get Error 7 when I try to Flash a Custom ROM:
A: Flash 3.1 TWRP Recovery, the custom recovery you have flashed, does not support the custom ROM you want to flash.
Q: I no longer have open command prompt here after intalling Windows 10 Creators update, I have Open Powershell instead, help?
A: Read the following webpage:
http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/
It provides a registry fix which adds/restores "open command window here" in Windows 10 Context Menu
Q: Custom Recovery 3.1 is in Chinese, how do I change it to English?
A: See the following images
Tested on Windows 10 x64 Pro with Creators Update, should work for Windows 7/8 as well.
If this guide helped you, please buy me a beer, thanks!
http://paypal.me/mariosffx

MariosFFX said:
The recoveries I post are and tested for Lenovo Z2 Zuk Z2 Pro ONLY!
Requirements:
Unlocked phone bootloader
and your phone booted in fastboot mode, otherwise it will not work.
Recovery.img is the same recovery found on Lenovo forums (link below)
Download from MEGA
https://mega.nz/#!zJhFCKRa!7FDyDKkqEL3bgz-lYBMf_Lj0RoMyzubg9tiZC3z9ttg
Images are in thumbnails, click on them to enlarge
Short guide:
1) Simply extract the zip
2) Open cmd.exe and cd to the directory you extracted
3) Put your phone in fastboot mode by shutting down your phone, if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
4) Paste the following commands:
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
You should get the same results I got:
Long guide for newbies with Windows 10 [the same might be for Windows 7/8]:
1) Download the zip I have uploaded and extract it to a folder with your favorite archive manager [I use WinRAR] and open it
2) Hold Shift and Right Click on empty space in the folder
3) Left click on Open command window here or open command prompt here
4) Put your phone in fastboot mode by shutting down your phone, power it on and if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
5) Paste the following commands by copying one line each time
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
Contents of Uploaded RAR/Zip Archive:
adb.exe & fastboot.exe taken from adb-setup-1.4.3 zip/rar file, which was found on Google, don't have a source link
drivers where taken from ZUK_UsbDriver_1.0.6 zip/rar from a guide which was found on google, don't have a source link
recovery images where taken from the sources below
Sources & Thanks:
Recovery 3.0.8 was taken from:
https://forum.xda-developers.com/le...t/twrp-recovery-zuk-z2-standard-pro-t3415395/
credits go to @raimondomartire
Recovery 3.1 was found on official Lenovo Forums:
http://bbs.lenovomobile.cn/z2pro/t508552/
Google translated Lenovo Forum Page:
https://translate.google.com/transl...n&u=http://bbs.lenovomobile.cn/z2pro/t508552/
Q&A:
Q: I do the same steps you did, in command prompt after pasting your commands I get the following: "< waiting for device >
or I wait for long periods of time or I get a [ERROR] message
A: Chances are 100%, you have the wrong drivers or not drivers installed, most devices use their own drivers for fastboot mode or adb/fastboot commands
If you have a Lenovo Zuk Z2 Pro like me, your device needs to be identified as "ShenQi Composite ADB Interface" in device manager.
Not "Android" or "Android ADB Interface" and because of that fastboot does not identify your device at all
Q: Why do you use 2 commands (fastboot flash and fastboot flash) instead of one?
A: I am not 100% sure but I think fastboot flash recovery, flashes the recovery image you have selected [permanently, until you flash a different one] in your device and you can boot into it anytime you want without using a PC
and the second boots your phone with the recovery image but does not flash it, meaning you keep the stock or the one you have flashed in the past.
So I use the first commmand to permanently flash the recovery and the second to boot the phone in recovery mode without using any phone button combinations to boot into, saves me the time and hassle.
Q: Why use Chinese Custom Recovery instead of an English one?
A: This recovery has Chinese and English Language support. However, if you go to the translated google forum link which I have posted below, the thread's title is: Z2 pro Brush] [zuk z2Pro] Twrp Recovery 3.10 update, support Andrews 7.0 7.1 7.1.2ROM
So I think, Recoveries need to also support the custom ROMS you want to flash, also it is taken from official lenovo forums and chances are they have added more features and fixes.
For example using 3.0.8 recovery I couldn't install LineageOS 14.1 custom rom, I was getting Error 7 when I was trying to flash
Q: I get Error 7 when I try to Flash a Custom ROM:
A: Flash 3.1 TWRP Recovery, the custom recovery you have flashed, does not support the custom ROM you want to flash.
Q: I no longer have open command prompt here after intalling Windows 10 Creators update, I have Open Powershell instead, help?
A: Read the following webpage:
http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/
It provides a registry fix which adds/restores "open command window here" in Windows 10 Context Menu
Q: Custom Recovery 3.1 is in Chinese, how do I change it to English?
A: See the following images
Tested on Windows 10 x64 Pro with Creators Update, should work for Windows 7/8 as well.
If this guide helped you, please buy me a beer, thanks!
http://paypal.me/mariosffx
Click to expand...
Click to collapse
Thanks for this.
I'm waiting for delivery of a Z2 Pro and getting necessary stuff ready.
The Mega link wants a Decrypt key.

bluegrass55 said:
Thanks for this.
I'm waiting for delivery of a Z2 Pro and getting necessary stuff ready.
The Mega link wants a Decrypt key.
Click to expand...
Click to collapse
check again, the link is with decryption key.
I have double checked and made sure it was with the key.

I've tried again on Chrome,IE and Firefox but still get Decrypt message.

Do you copy and paste the link or you click on it?
Seems to me you copy and paste it.
Because the link is way too big, xda forums shorten it (notice the dots).
Click the link don't copy and paste iit

Finally managed to download it.
I clicked on the link in Chrome & it worked. Firefox didn't like it.
Thanks for the help.

fastboot claims to work, but doesn't
Code:
[email protected] ~/Downloads> fastboot -i 0x2b4c flash recovery twrp.img
target reported max download size of 1610612736 bytes
sending 'recovery' (18372 KB)...
OKAY [ 0.525s]
writing 'recovery'...
OKAY [ 0.145s]
finished. total time: 0.670s
[email protected] ~/Downloads> fastboot -i 0x2b4c reboot
rebooting...
finished. total time: 0.071s
Yet it goes back stock recovery. I've tried many variations of these commands, and always get the same results.

Philo.Phineas said:
Yet it goes back stock recovery. I've tried many variations of these commands, and always get the same results.
Click to expand...
Click to collapse
I am having problems with this Chinese twrp why not get fixed in the bootloader nor accept after even running without installing the program supersu via twrp

Hello All,
So originally I had TWRP 3.0 on my Z2 pro, and i attempted to just install the 3.1 img file from it(per another instructional video from the 7.1 mokee thread), and after installing the recovery file, my phone restarted, however now when I attempt to go into Recovery mode from the boot menu, my phone just goes to a blank screen.
I've tried to flash the image from CMD to see if i could essentially "re flash" 3.1 TWRP, but I always get this message(see attached image). What am i typing in wrong in CMD? As you can see, the directory name is right, as well as the fastboot code. I'm also IN fastboot mode on my phone already. I changed the file name of the folder containing the recovery from it's orginal name to make it shorter, but that should not matter at all. It seems as if CMD can't find the folder though?
Well XDA won't let me post a damn picture(how am i supposed to ask for help if i can't show people what im doing), so I guess if someone would PM me i can post the image.

People do you try to flash the recoveries right after unlocking your bootloader?
Because if you can't flash the recovery and it goes back to stock, it means you haven't fully unloxked your bootloader.
Make sure you run the last following command when you unlock your bootloader
Code:
fastboot -i 0x2b4c oem unlock-go
Then follow my guide here.
Also bootloader unlock tutorial here:
https://zukfans.eu/community/threads/zuk-z2--unlock.62/
Its for Zuk Z2, but the instructions are also for Z2 Pro.

MariosFFX said:
rl].
Click to expand...
Click to collapse
Any idea about what's happening with the situation in my post by chance? When I try to flash from CMD i get this text. "Z2 is not recognized as an internal or external command, operable program or batch file"
"Z2" is the name of the folder that contains the recovery image, so it seems like it's not finding it.

which files about phone mobile data at a TWRP BACKUP ? i see a lot of files inside of a twrp backup . i need to learn that . thanks.

jsto69 said:
Any idea about what's happening with the situation in my post by chance? When I try to flash from CMD i get this text. "Z2 is not recognized as an internal or external command, operable program or batch file"
"Z2" is the name of the folder that contains the recovery image, so it seems like it's not finding it.
Click to expand...
Click to collapse
Use directory names without spaces. Like c:\zuk and perform all operations from there.

Hello, this works fine very thx, but you have recent/new mix version?

[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

How to make Bank Application work on my unlocked K20 Pro Indian ROM?

as title ... How to make Bank Application work on my unlocked K20 Pro Indian ROM?
it was mi 9t pro and i switched to the Miui 11 Indian ROM.
kindly explain steps and include links if any.
appreciate help.

NaAZoOR said:
as title ... How to make Bank Application work on my unlocked K20 Pro Indian ROM?
it was mi 9t pro and i switched to the Miui 11 Indian ROM.
kindly explain steps and include links if any.
appreciate help.
Click to expand...
Click to collapse
Flash magisk --> magisk hide.
Just watch that guy on YouTube.
https://youtu.be/MapOXLH5Gkg

Kollachi said:
Flash magisk --> magisk hide.
Just watch that guy on YouTube.
https://youtu.be/MapOXLH5Gkg
Click to expand...
Click to collapse
How to flash magisk?
kindly provide steps & links if any
Sent from my Redmi K20 Pro using XDA-Developers Legacy app

NaAZoOR said:
How to flash magisk?
kindly provide steps & links if any
Sent from my Redmi K20 Pro using XDA-Developers Legacy app
Click to expand...
Click to collapse
https://forum.xda-developers.com/k20-pro/how-to/guide-redmi-k20-pro-unlock-root-t3974127

Kollachi said:
https://forum.xda-developers.com/k20-pro/how-to/guide-redmi-k20-pro-unlock-root-t3974127
Click to expand...
Click to collapse
the below quote includes steps to flash TWRP & Magisk from the link you provided, my question is:
after rooting via Magisk, am i able to get OTA updates from Xiaomi for the device normally or just like the old days, once rooted no more updates to come?
and is it sure that bank app will work normally after flashing Magisk??
FLASHING TWRP & ROOTING
Alright, you got all the software tools and now we're ready to proceed with flashing TWRP and Magisk.
With your phone powered on normally, plug your device into your computer with the USB cable.
Pull down on the screen to display the notifications. One of them should read "Android System" and indicate how the phone is interacting with your computer as a connected device. Switch it to "File Transfer." Your phone should now show up as a drive on your computer.
Open the "Redmi K20 Pro" drive on your computer and then open the "Internal shared storage" folder (it should be the only folder).
Drag and drop the Magisk.zip and the Disable-Force-Encryption-Treble.zip into that folder.
**SIDE NOTE: Some guides suggest that you wait until you're in TWRP to transfer these files. That's fine. To do so, wait until you're in the TWRP interface and then select "Mount" and "Enable MTP." Your phone's internal storage should appear as a device on your computer and you can then transfer the .zips.
Once transferred, unplug your phone from the computer and power it off.
Enter into Fastboot mode by pressing and and holding down the Volume Down button and the Power button at the same time. It may take several seconds. It will vibrate and then boot your phone into Fastboot mode.
Next, connect your phone to your computer with the USB cable.
Once you connect your phone to the computer via USB, you should hear the computer recognize the phone but you may not see it show up as a drive. That's okay.
Go to your computer and open a command line interface in the ADB folder (if you're sticking with my recommendation, it will be the "platform-tools" folder).
**NOTE: If you chose the Auto Install option of TWRP, you can simply double-click the file "flash_twrp.bat" and then skip to the next section (TWRP INTERFACE).
**TRICK: Go to the folder where you have the ADB file adb.exe and click in the file pathway (where it says "C:\Users\Username\Downloads\platform-tools_r29.0.4-windows\platform-tools" or whatever). Highlight and delete that file pathway, and instead type "cmd". Hit enter and it will open a terminal window already in the proper directory.
**SIDE NOTE: If you installed ADB/Fastboot universally, you can simply open the command line interface by clicking on Start and typing "cmd" to open a terminal window. Once in the terminal window, you can "cd" or change directory to the one where you have ADB. Also, you can use Powershell, but you may need to preference each Fastboot command with "./."
In that terminal window, make sure you're in the folder with adb.exe and then type this command:
fastboot devices
This command looks to make sure that the Fastboot platform recognizes your device. Next to "Fastboot Devices," you should see a series of numbers and letters. That series of numbers and letters is your phone identifier.. If you do not see any numbers/letters, then Fastboot does not see your phone and you need to troubleshoot the situation.
Next, type in the following command:
fastboot flash recovery twrp.img
What this is doing is identifying what platform to use (fastboot), telling it what you want to do (flash), in which directory you want to perform that action (recovery), and what file to use to flash it (twrp.img). It is important to note that, depending on how you installed TWRP, the .IMG file may be called "recovery.img" or "twrp.img" or some variation of the TWRP version number. You can either rename the file to "twrp.img" or you can type in the entire filename.
Once you hit enter, it will read something like:
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.437s]
writing 'recovery'...
OKAY [ 0.254s]
finished. total time: 1.696s
Once it's finished, enter this command to boot into the temporary TWRP recovery operating system:
fastboot boot twrp.img
Once you hit enter, it will read something like:
downloading 'boot.img'...
OKAY [ 1.428s]
booting...
OKAY [ 0.138s]
finished. total time: 1.566s
TWRP INTERFACE
Unplug your phone from the USB. The screen will go black and you may see the "Redmi" logo come on the screen. After a few seconds, the TWRP title page will appear. Once the TWRP operating system powers on, you may be presented with the option to enter a PIN code (if you previously had one on your phone) or a passcode. Enter the PIN or code to get into the TWRP interface.
Once in TWRP, you will have several options. Click "Install" and scroll to the bottom of the file list to find the magisk.zip that you transferred onto your phone. Go ahead and swipe right to install it. Once the installation is complete, click "Reboot System" to power the phone back on normally.
That's it. Your Redmi K20 Pro should now be rooted.
If there are any problems, start the process over from the Fastboot interface on your computer (where you flashed TWRP onto your phone with "fastboot flash recovery twrp.img"). Go through the same process, but before you install the Magisk.zip, first install the Disable-Force-Encryption-Treble.zip.
Click to expand...
Click to collapse

NaAZoOR said:
the below quote includes steps to flash TWRP & Magisk from the link you provided, my question is:
after rooting via Magisk, am i able to get OTA updates from Xiaomi for the device normally or just like the old days, once rooted no more updates to come?
and is it sure that bank app will work normally after flashing Magisk??
Click to expand...
Click to collapse
I don't know about OTA. I don't have Miui on my device. And bank apps work for me with magisk hide.

miflash error: not catch checkpoint (\$fastboot -s .*lock), flash not done -> HELP?!

miflash error: not catch checkpoint (\$fastboot -s .*lock), flash not done -> HELP?!
Hello,
I unlocked my Mi8 and successfully installed Lineage on it.
After trying to install Magisk, my phone only boots into fastboot (and mi recovery, but that's not very helpful).
fastboot boot twrp.img results in error :
FAILED (remote: Failed to load/authenticate boot image: 00000050)
I tried MIFLASH by
1) downloading, dezipping and starting newest miflash (2020.3.14.0)
2) installing drivers
3) downloading and dezipping MIUI-fastboot-ROM
4) entering path* into miflash, refresh and flash (already tried all options "clean all" to "clean all and lock")
*) path to the folder that includes among others flash_all.bat
all this results in error:
not catch checkpoint (\$fastboot -s .*lock), flash not done
Nothing changed with the phone, still the same error.
While wanting to review the logs, I clicked in miflash on log/flash log. The log did not say anything helpful, but the error code of fastboot boot twrp.img changed to command write failed (Unknown error). Nothing else changed.
UPDATE: changed back to previous error (remote: Failed to load/authenticate boot image: 00000050)
If you have any idea or need any more information, please tell me!
I need that phone and cannot afford to terminally brink it!!
I did not find much online, did no one else had this problem??
THANK YOU!
PS: Using lenovo-laptop with quite vanilla win10 (and not so vanilla kubuntu dualboot, but miflash only supports windows)
MIFLASH-log says:
Code:
[14:37:14]:lsusb path:"C:\Users\<>\Downloads\MiFlash20200314\MiFlash20200314\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[14:37:14]:GetScriptDevices
[14:37:15]:FlashingDevice.flashDeviceList.Remove ab6ee6a0
[14:37:15]:add device ab6ee6a0 index 1
[14:37:15]:Thread start,thread id 5,thread name ab6ee6a0
[14:37:15]:start process id 2524 name cmd
[14:37:15]:Thread stopped, thread id 5, thread name ab6ee6a0
UPDATE:
what would the world be without mysteries. Though I cannot really accept them in the IT sector, I cannot really explain, why "everything" works now.
The error of miflash still exists, but fastboot works.
I tried booting and flashing the lineage boot.img instead of twrp.img as well as miflash about every five minutes. I do not think it was the latter, though.
I am still curious on that matter, but having everything working is more important.
Thank you anyway.

Never encountered that error however, if you have Lineage installed i have to wonder how or why your phone is able to boot into mi recovery ? You should have a custom recovery installed (twrp, orangefox .. something)
If you have a ryzen laptop - see the thread about ryzen cpu - they have some issues with recognising properly devices via usb - solved by using a hub.
There is no need to use miflash to flash the fastboot miui rom - you can do it from command line in both windows and linux. Once you decompress the fastboot tar.gz, you have .bat and .sh files in the folder - miflash runs those exact files. Just install adb and fastboot on kubuntu and run your choice of script (flash_all, flash_all_lock, etc.) this has the added benefit of not needing odd drivers in windows (last time i used miflash it complained about some .net stuff that i had to manually install).
Since normally you would install twrp i have to wonder if by any chance mi-recovery is not checking the boot image before flashing it ... not sure, or maybe it had something to do with the FBE of lineage since there was no recovery in place to decrypt the partitions, if i remember correctly, the boot image needs to be signed with the verity key. The log snippet you provided doesn't tell anything as it has no error messages or anything.
Either way, not sure how what you brutforced to get it working but glad it solved itself, however, if you still have mi-recovery instead of a custom one, i would suggest you backup the device, flash MIUI without locking the bootloader, installing twrp (not just booting it) and reinstalling lineage from there. (all this can be done from your kubuntu install so you avoid driver and other windows shenanigans)
to install adb and fastboot it's just a question of sudo apt install adb fastboot
either tar -xvzf the archive of the fastboot image or just extract it from the file manager
open a terminal in the extracted folder (where the bat and sh files are)
put the phone in fastboot mode, connect via usb and do a "fastboot devices" just to make sure the device shows up
./flash_all.sh (this does the exact same thing as the clean option in miflash - just open the script and take a look through it)
Once the flash is done and the phone reboots, skip through all the setup steps just so miui loads up then reboot to fastboot
get twrp from their website, open terminal where it is downloaded and "fastboot flash recovery <name_of_file>.img"
once the command finishes do a "fastboot boot <name_of_file>.img" and once you are in twrp, go yo wipe, do a factory reset, back, advanced wipe and select the caches, back, format data, type yes, back to the main menu of twrp and reboot recovery, this should boot you back into twrp but this time the one that is flashed on the device.
from here on install rom of choice and magisk as usual (use the install option in twrp tho, don't unpack the zip)
Had the phone for 2 years and i flashed different roms on it almost weekly since the wait time to unlock the bootloader expired and never had an issue with this workflow and it saves you from having to use windows. Even for unlocking the bootloader, in case you ever lock it back up, you can use https://xiaomitool.com/V2/download (worked like a charm on linux)

sorfat said:
Never encountered that error however, if you have Lineage installed i have to wonder how or why your phone is able to boot into mi recovery ? You should have a custom recovery installed (twrp, orangefox .. something)
If you have a ryzen laptop - see the thread about ryzen cpu - they have some issues with recognising properly devices via usb - solved by using a hub....
Click to expand...
Click to collapse
Thank you for your detailed reply!
Of cause, in order to install lineage, I used TWRP. But I somehow did not install it, but used fastboot boot twrp.img in order to manually temporary boot twrp every time I need it. It was not intentionally at first (did do
"fastboot flash recovery <name_of_file>.img"
Click to expand...
Click to collapse
) but I learned to like the mi recovery for it's wiping and being able to use with the keys (not touch, since I managed to disable touch once before that). Mi recovery does not allow flashing at all, so no worries there^^
I have read the ryzen thread before posting, that's why I included my hardware. Not sure, if Lenovo has ryzen, mine does not.
Why I did not think of just running the script in kubuntu instead of hassling with windows, I do not know. Guess it does have something to do with the wood in front of all the trees.
I have the phone for about one and a half week and flashed it at least once a day :laugh:
But I hope to neither lock it again (twice is sweaty enough) nor have to flash it every week.
Thank you very much, if I ever lock myself out again or get another phone to set up, I will defintely reread this post!
btw: is there no way in xda to close a thread?

Moto E6 Flashboot Flash Magisk_Patched Recovery Image not signed or corrupt

Per https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery installing Magisk as recovery due to No RAMDISK on my Moto E6.
"If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition.
Click to expand...
Click to collapse
The phone was successfully unlocked per Motorola Unlock Your Bootloader.
Magisk_Manager generated magisk_Patched Img. Recovery_Image was extracted on PC with WinRAR from Get Droid Tips, Moto E6 Stock Collection, current download matches my Moto E6 build#, PPB29.73-81. My model is XT2005-5. To avoid corruption, I used ADB, not MTP to transfer files. ADB pushed WinRAR Extracted recovery image, and ADB pulled magisk_Patched image.
However, the Execution of ADB Fastboot flash recovery was "Image not signed or corrupt" per the following log:
Code:
C:\adb>fastboot flash recovery C:\adb\magisk_patched_k54ii.img
target reported max download size of 535822336 bytes
sending 'recovery' (16341 KB)...
OKAY [ 0.533s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.285s]
finished. total time: 0.820s
Why am I getting a corrupt image? Does anyone recommend a better Stock Recovery-Image source, perhaps where I can confirm the hashtag of the download and image extraction? TWRP does not seem to be an option for MotoE6/ No-RAMdisk devices.

I don't recommend images from Get Droid Tips, Moto E6 Stock Collection while they have the build numbers for the downloads, they did not show that there are various model numbers for the Moto E6. My guess is this is the likely cause of the "corrupt" image message from my flash recovery attempt.
I will use a stock image from https://mirrors.lolinet.com/firmware/moto/surfna/official/

kem827 said:
Per https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery installing Magisk as recovery due to No RAMDISK on my Moto E6.
The phone was successfully unlocked per Motorola Unlock Your Bootloader.
Magisk_Manager generated magisk_Patched Img. Recovery_Image was extracted on PC with WinRAR from Get Droid Tips, Moto E6 Stock Collection, current download matches my Moto E6 build#, PPB29.73-81. My model is XT2005-5. To avoid corruption, I used ADB, not MTP to transfer files. ADB pushed WinRAR Extracted recovery image, and ADB pulled magisk_Patched image.
However, the Execution of ADB Fastboot flash recovery was "Image not signed or corrupt" per the following log:
Code:
C:\adb>fastboot flash recovery C:\adb\magisk_patched_k54ii.img
target reported max download size of 535822336 bytes
sending 'recovery' (16341 KB)...
OKAY [ 0.533s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.285s]
finished. total time: 0.820s
Why am I getting a corrupt image? Does anyone recommend a better Stock Recovery-Image source, perhaps where I can confirm the hashtag of the download and image extraction? TWRP does not seem to be an option for MotoE6/ No-RAMdisk devices.
Click to expand...
Click to collapse
I don't know why this occurs, but it's "normal". What the installer guide doesn't tell you is:
- when you flash the patched recovery, you can't then use fastboot to get to recovery mode (well, you can...but it doesn't work). Instead, you MUST use the fastboot navigation keys (vol up/down and power) to go to recovery. When you do that, you'll boot the whole system into a rooted state (you won't see a recovery menu of any kind).
- at least on my phone, when you do this you are rooted for exactly one session. Next time you boot, the recovery image you flashed will be replaced with the "factory" original one. There is a work-around for this, but that's the behavior.
- if you are trying to install EdXposed, I don't believe you can do so just with the recovery-image method. You have to install the whole of Magisk (many MB) and I haven't figured out how to do this yet. (many, many false starts...)

dav0dav0 said:
I don't know why this occurs, but it's "normal". What the installer guide doesn't tell you is:
- when you flash the patched recovery, you can't then use fastboot to get to recovery mode (well, you can...but it doesn't work). Instead, you MUST use the fastboot navigation keys (vol up/down and power) to go to recovery. When you do that, you'll boot the whole system into a rooted state (you won't see a recovery menu of any kind).
- at least on my phone, when you do this you are rooted for exactly one session. Next time you boot, the recovery image you flashed will be replaced with the "factory" original one. There is a work-around for this, but that's the behavior.
- if you are trying to install EdXposed, I don't believe you can do so just with the recovery-image method. You have to install the whole of Magisk (many MB) and I haven't figured out how to do this yet. (many, many false starts...)
Click to expand...
Click to collapse
Ok, Thanks. Looks like my attempt to flash ( from Get Droid Tips, Moto E6 Stock Collection, ) was not the correct Moto E6 model. Phone boots still to the factory, and not rooted, but has a "bad key" error.. Boot to Recovery just responds "no command"
I did find now download the correct image from https://mirrors.lolinet.com/firmware/moto/surfna/official/ (matched by the Correct Moto E6 XT2005 model and build) but now ADB does not want to push or pull files. Unsure how to proceed.

I got my "stock ROM" by using Moto's "Rescue and Smart Assistant" tool -- it interrogates the phone, and lets you download the correct ZIP file automatically. Obviously, you do'nt want to actually install the ZIP -- you just want it downloaded. It puts the ZIP into a location it discloses, so you can find it. ;-)
Was ADB pushing/pulling files before? That's really weird if it did...but in any case, when the phone is booted to the normal system you can just copy the files over to the phone via the standard USB file sharing connection. If that's not working, you may need to reainstall the USB drivers on your PC. Don't forget to enable USB file sharing on the phone!

dav0dav0 said:
I got my "stock ROM" by using Moto's "Rescue and Smart Assistant" tool -- it interrogates the phone, and lets you download the correct ZIP file automatically. Obviously, you do'nt want to actually install the ZIP -- you just want it downloaded. It puts the ZIP into a location it discloses, so you can find it. ;-)
Was ADB pushing/pulling files before? That's really weird if it did...but in any case, when the phone is booted to the normal system you can just copy the files over to the phone via the standard USB file sharing connection. If that's not working, you may need to reainstall the USB drivers on your PC. Don't forget to enable USB file sharing on the phone!
Click to expand...
Click to collapse
ADB was pushing and pulling. I found the XDA posting that might help solve this official-tool-windows-adb-fastboot-and-drivers-15-seconds-ADB-installer-v1-4-3.2588979/. I'll update my drivers per the video found here, and try again.
While deleting some old Samsung Drivers was probably necessary, the error remained. Searched and found that the directory "/SD Card" is incorrect, even though topjohnwu.github failed to explain that "SD Card" is not the same folder as seen in the windows USB Link. It is the Internal SD Card which the ADB uses, which I find on windows at "Internal Shared Storage/Download". Once I moved the file on my phone to that folder , I was able to Pull the file using the command "ADB Pull \Sdcard\download.."

Reflashed my patched majesk recovery image. But, I can not boot recovery. Fastboot gives me a "no command" message. Screen always displays "bad key" on any boot. Holding power and tapping upkey does nothing in attempt to Boot to Recovery.

kem827 said:
Reflashed my patched majesk recovery image. But, I can not boot recovery. Fastboot gives me a "no command" message. Screen always displays "bad key" on any boot. Holding power and tapping upkey does nothing in attempt to Boot to Recovery.
Click to expand...
Click to collapse
I believe that the "bad key" message will occur whenever you have an unlocked bootloader. There is a way to hide it (search within XDA forums, you'll find several posts), but I leave it as is so I get a positive indicator of where I really am.
You say "Fastboot gives me a 'no command' message": I think what you mean is "when I go from Fastboot to Recovery mode, a get a 'no command' message." -- because the only time I've ever seen that message is under the Android-robot icon, which indicates "you're in stock recovery mode." When you are there, you should be able to get to the command menu by clicking power-on and volume-up simultaneously. If you don't, do a power cycle and try again.
You'll know you've booted the root mode when you don't see the "bad key" message, but instead see something like "Unsigned or corrupt image" when you go into recovery mode (and you won't see the normal Android icon or "no command" message).
In my experience with this phone, if you are in bootloader and use your PC to get you to recovery mode (fastboot reboot recovery from the command line), it may not work. The only way to reliably get into real recovery mode is to do a power cycle on the phone, go into fastboot, and then use the phone's buttons to get to recovery.
Also note that if all that you have done is the Magisk modify-recovery-image strategy, you get one (and only one) attempt to run as rooted. Any time you go thru a power-on reset of the phone, your modded-recovery image will be erased and replaced with the factory one.
In my various runs, I've determined that once you've achieved root access you can soft-reboot the phone and remain in root. Anything you install there will survive soft-reboots. But if you do a hard reboot, next time you go into root you may have to reinstall EdXposed and supporting libraries, and reactivate stuff for everything to work.
Sadly, the Xposed module I was doing all this for doesn't seem to work under EdXposed, even though it's supposed to. So it was a days-long wild goose chase.

dav0dav0 said:
I believe that the "bad key" message will occur whenever you have an unlocked bootloader. There is a way to hide it (search within XDA forums, you'll find several posts), but I leave it as is so I get a positive indicator of where I really am.
You say "Fastboot gives me a 'no command' message": I think what you mean is "when I go from Fastboot to Recovery mode, a get a 'no command' message." -- because the only time I've ever seen that message is under the Android-robot icon, which indicates "you're in stock recovery mode." When you are there, you should be able to get to the command menu by clicking power-on and volume-up simultaneously. If you don't, do a power cycle and try again.
You'll know you've booted the root mode when you don't see the "bad key" message, but instead see something like "Unsigned or corrupt image" when you go into recovery mode (and you won't see the normal Android icon or "no command" message).
In my experience with this phone, if you are in bootloader and use your PC to get you to recovery mode (fastboot reboot recovery from the command line), it may not work. The only way to reliably get into real recovery mode is to do a power cycle on the phone, go into fastboot, and then use the phone's buttons to get to recovery.
Also note that if all that you have done is the Magisk modify-recovery-image strategy, you get one (and only one) attempt to run as rooted. Any time you go thru a power-on reset of the phone, your modded-recovery image will be erased and replaced with the factory one.
In my various runs, I've determined that once you've achieved root access you can soft-reboot the phone and remain in root. Anything you install there will survive soft-reboots. But if you do a hard reboot, next time you go into root you may have to reinstall EdXposed and supporting libraries, and reactivate stuff for everything to work.
Sadly, the Xposed module I was doing all this for doesn't seem to work under EdXposed, even though it's supposed to. So it was a days-long wild goose chase.
Click to expand...
Click to collapse
Thanks for you help. I finally got a correct flash and boot to a rooted recovery. Looks like Top Johns' Magisk Instruction Page needs some corrections: Like explaining that "SDCard" shows as [internal storage] on the PC and that the external Storage is the [SD Card] directory. He fails to tell to rename the magisk_patched file to "recovery. img" before flashing it. (An obvious error but easy to overlook when you are following an unfamiliar command syntax) . The "bad key" message and "corrupt signature" message explanation is useful info too. He fails to let you know how to even check for a successful root

kem827 said:
Thanks for you help. I finally got a correct flash and boot to a rooted recovery. Looks like Top Johns' Magisk Instruction Page needs some corrections: Like explaining that "SDCard" shows as [internal storage] on the PC and that the external Storage is the [SD Card] directory. He fails to tell to rename the magisk_patched file to "recovery. img" before flashing it. (An obvious error but easy to overlook when you are following an unfamiliar command syntax) . The "bad key" message and "corrupt signature" message explanation is useful info too. He fails to let you know how to even check for a successful root
Click to expand...
Click to collapse
And to add to the fun...Magisk Manager has/had a bug where it will tell you that your phone *doesn't* have a RAMdisk but it actually does....sometimes. So you might try to do the boot.img patch instead of the recovery.img one--that would give you a permanent root, rather than a transitory one. I didn't bother to check that out, as the whole reason I was rooting was to use an Xposed module that doesn't seem to work.
Let me know if you try that strategy out and it works...

kem827 said:
Thanks for you help. I finally got a correct flash and boot to a rooted recovery. Looks like Top Johns' Magisk Instruction Page needs some corrections: Like explaining that "SDCard" shows as [internal storage] on the PC and that the external Storage is the [SD Card] directory. He fails to tell to rename the magisk_patched file to "recovery. img" before flashing it. (An obvious error but easy to overlook when you are following an unfamiliar command syntax) . The "bad key" message and "corrupt signature" message explanation is useful info too. He fails to let you know how to even check for a successful root
Click to expand...
Click to collapse
The instructions assume that you are somewhat familiar with Android, adb and fastboot. There's plenty of info and guides on that around the web, so it would be redundant for John to add that too (and the instructions would become way too long).
There are also many devices specific things that he's never gonna be able to cover. The fractured nature of Android is just too much for that...
If you have suggestions though, you can always open a PR on GitHub with your proposed changes and clarifications.

dav0dav0 said:
Magisk Manager has/had a bug where it will tell you that your phone *doesn't* have a RAMdisk but it actually does....sometimes
Click to expand...
Click to collapse
That's not a bug with Magisk, but yet another issue with Android's fractured ecosystem. John actually covers that in his documentation. Check this page, and in particular the last paragraph:
https://topjohnwu.github.io/Magisk/boot.html