Develop Bugs

[GUIDE][FIX]Cant unlock bootloader? Read here for a Fix

Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.

That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k

I'm on 2.18 and rooted. Problem is, I uninstalled or disabled a bunch of ASUS apps, will I have an issue if I use SuperSU to unroot and try to restore or upgrade my phone to 2.19?
Also, I have model number ASUS_Z00AD. Is this firmware OK to install on my phone?

cmendonc2 said:
That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
Click to expand...
Click to collapse
Fixed.

edit: nvm...

Both download links link to the same file. splashscreen.img

Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love

jpacleb85 said:
Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love
Click to expand...
Click to collapse
LOL... Gotta love the devs who tinker on here... Now we might actually get a recovery that will do nandroid backups in case of those "little" mistakes/problems that crop up from time to time...

MiCmAsTa said:
Both download links link to the same file. splashscreen.img
Click to expand...
Click to collapse
Fixed.

This is probably a silly question, but I have the ZE550ML and the latest update is 2.18, meaning that unlocking the bootloader it is still not possible can I install droidboot.img(fastboot img) from the 2.19 ZE551ML on my device? Or that will just hard brick my device?
Let me know your thoughts on this.
Continue the great work XDA crew =)

I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated

PsychoKilla666 said:
I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated
Click to expand...
Click to collapse
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.

rafyvitto said:
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.
Click to expand...
Click to collapse
Link please? and how to?

error
rafyvitto said:
Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.
Click to expand...
Click to collapse
I follow this method and received the following error on CMD
writing 'fastboot'....
FAILED (remote: falsh_cmds error!
Finished. total time: 0.830

im on 2.20 and it wont let me do anything.. i get the white boot screen instead of black but bootloader doesnt exist and it wont download twrp any suggestions?

Success
My phone's recovery stopped working, and the bootloader was locked, but I found this thread. I think I was able to get it working.
I extracted the droidboot.img from the file in the OP.
I copied the droidboot.img to my working directory, and tried to flash it.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.661s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.826s
Ok, I got the error. Maybe the "unlock" command will work.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.203s]
finished. total time: 0.204s
Same output as the last hundred times I tried to run it.
I rebooted the phone.
Code:
C:\myworkingdirectory>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.108s]
finished. total time: 0.109s
I put the phone into the bootloader mode. (For anyone reading, to get into the bootloader, turn the phone completely off. Hold the power button until it vibrates. Then hold the volume up key.)
I ran the unlock command twice.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.291s]
finished. total time: 0.326s
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.216s]
finished. total time: 0.216s
Then I tried to flash the image again.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.690s]
writing 'fastboot'...
OKAY [ 0.692s]
finished. total time: 1.384s
No error?! I have progress!
------
I believe my bootloader is unlocked. Let me try to flash the recovery. (My recovery was corrupted longggg before doing this.)
Code:
C:\myworkingdirectory>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11676 KB)...
OKAY [ 0.579s]
writing 'recovery'...
OKAY [ 0.571s]
finished. total time: 1.153s
No permission error! (Before this, I would usually have gotten an error that says "FAILED (remote: Permission denied".)
---- Important Notes ----
NO WHITE BACKGROUND IN BOOTLOADER.
Many people have reported seeing an inverted background in the bootloader. I don't have that.
TRIPLE DOTS IN COMMAND PROMPT
The triple dots you see when I run the unlock command are actually there. They are not placeholders.
------------
Right now I'm booting into recovery mode to flash a ROM to the phone. I'll update if I get the phone working.

Root + Twrp Recovery Asus Zenfone Selfie (ZD551KL)(Z00T)

Pre-Requirement File for Selfie
★ Zenfone Selfie with Unlocked Bootloader ★
★ Zenfone Selfie Recovery ToolKit ★
How to Install TWRP Recovery On Zenfone Selfie
Step 1. Download and Install ADB fastboot tool on PC.
Step 2. Enable USB Debugging mode on ZenFone Selfie (Settings>Developer Options> USB Debugging)
Step 3. Extract Zenfone Selfie Recovery ToolKit
Step 4. Connect ZenFone Selfie with your PC
Step 5. At toolkit Folder Press shift + mouse right click > open command here
Step 6. Type these command in sequence (enter after each line):
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot oem reboot -recovery
Step 9. Wait for the device restart and entered the recovery
Step 10. Done
Asus Zenfone Selfie Easy Root
::::::: Procedure Rooting Asus Zenfone Selfie:::::::
# go to twrp recovery by pressing (power button+ volume up
button)
#select Install from sd card > install zip from SD card > select – Root Zenfone Selfie.zip> yes.
#then a process will occur.
# wait untill it finished.
#then reboot your Asus Zenfone Selfie
Congrats, you have successfully Rooted Asus Zenfone Selfie
:good::highfive:
DISCLAIMER: I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE IN THE PROCESS. DO IT AT YOUR OWN RISK.

did u try on prerooted rom zenfone selfie ?

Hey will this work for Z00UD ?

pls help me , its stuck on
D:\DwnlData\asus_zenfone_selfie_recovery_toolkit>adb reboot bootloader
D:\DwnlData\asus_zenfone_selfie_recovery_toolkit>fastboot flash recovery recover
y.img
< waiting for device >
and on my Asus selfie just saw
Fastboot Mode!!!
and stuck on asus logo (

TWRP ?
Hi everyone !
So I tryed to install CM on my Asus zenfone (Z00UD) and everything worked with no problems until the fastboo oem reboot-recovery.
So I tryed to reboot while pressing the VOLUME DOWN key and i get to the original recovery mode.
My phone is still booting to the usual android when I boot without going in recovery.
So I guess TWRP flash didn't worked as excepted, but i remember it showing completed.
Is there a way to verify that TWRP isn't installed so i can re install it ?
Or is it another problem ?

Hiroyt01 said:
Hi everyone !
So I tryed to install CM on my Asus zenfone (Z00UD) and everything worked with no problems until the fastboo oem reboot-recovery.
So I tryed to reboot while pressing the VOLUME DOWN key and i get to the original recovery mode.
My phone is still booting to the usual android when I boot without going in recovery.
So I guess TWRP flash didn't worked as excepted, but i remember it showing completed.
Is there a way to verify that TWRP isn't installed so i can re install it ?
Or is it another problem ?
Click to expand...
Click to collapse
Hi,
Did you use all this three Codes???
"
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot oem reboot -recovery
"

reddyarunm46 said:
Hi,
Did you use all this three Codes???
"
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot oem reboot -recovery
"
Click to expand...
Click to collapse
Yes that is exactly what i used (Except replacing the recovery.img by the twrp.img name)
I also tryed fastboot oem reboot-recovery (without the space)

Hiroyt01 said:
Yes that is exactly what i used (Except replacing the recovery.img by the twrp.img name)
I also tryed fastboot oem reboot-recovery (without the space)
Click to expand...
Click to collapse
Instead of replacing the recovery.img by the twrp.img name jus replace "recovery" with the file name that you have downloaded!!!!
---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------
Hiroyt01 said:
Yes that is exactly what i used (Except replacing the recovery.img by the twrp.img name)
I also tryed fastboot oem reboot-recovery (without the space)
Click to expand...
Click to collapse
If you have downloaded from the above link in the thread then dont replace anything just use the codes.

reddyarunm46 said:
Instead of replacing the recovery.img by the twrp.img name jus replace "recovery" with the file name that you have downloaded!!!!
---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------
If you have downloaded from the above link in the thread then dont replace anything just use the codes.
Click to expand...
Click to collapse
I used dl.twrp.me/Z00T/ recovery (to get the latest), and I replaced "recovery.img" by "twrp-3.0.2-5-Z00T.img" in the fastboot comand line. I also put "twrp-3.0.2-5-Z00T.img" in the same folder as "recovery.img".
Should I try again the process with the recovery.img ?
Is it safe to try again to flash the recovery ? (I didn't try again the process because I don't know if it's safe)

Hiroyt01 said:
I used dl.twrp.me/Z00T/ recovery (to get the latest), and I replaced "recovery.img" by "twrp-3.0.2-5-Z00T.img" in the fastboot comand line. I also put "twrp-3.0.2-5-Z00T.img" in the same folder as "recovery.img".
Should I try again the process with the recovery.img ?
Is it safe to try again to flash the recovery ? (I didn't try again the process because I don't know if it's safe)
Click to expand...
Click to collapse
its all right....it worked for me..

Ok thanks, I'll try to flash again when getting home tonight.
Which of those 2 recovery do you recommend using ?

Hiroyt01 said:
Ok thanks, I'll try to flash again when getting home tonight.
Which of those 2 recovery do you recommend using ?
Click to expand...
Click to collapse
1st try with the recovery you downloaded for the thread . Then if you want to update you can do it as well using an TWRP App from play store ...

Can't install Twrp
I did as said above.
But I'm getting Failed to send data (Unknown error)
Please help me to install twrp

Asus zenfone selfie Z00UD android Marshmallow
Hello sir good afernoon,
Im Jon from Philippines and my problem is can you help me how to root my Asus zenfone selfie Z00UD running android marshmallow and install TWRP, because I dont know what to do. PLEASE help me sir.. GODBLESS

Stuck at "fastboot oem reboot -recovery"
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>adb devices
List of devices attached
FAAZCY041912 device
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>adb reboot bootloader
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (29436 KB)...
OKAY [ 0.924s]
writing 'recovery'...
OKAY [ 1.136s]
finished. total time: 2.061s
This is where I got problem:
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>fastboot oem reboot -recovery
...
FAILED (remote: unknown command)
finished. total time: 0.001s
how to resolve?
Please help me. Thanks.

ash_zairy said:
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>adb devices
List of devices attached
FAAZCY041912 device
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>adb reboot bootloader
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (29436 KB)...
OKAY [ 0.924s]
writing 'recovery'...
OKAY [ 1.136s]
finished. total time: 2.061s
This is where I got problem:
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>fastboot oem reboot -recovery
...
FAILED (remote: unknown command)
finished. total time: 0.001s
how to resolve?
Please help me. Thanks.
Click to expand...
Click to collapse
Same problem for me, did you solved it?

Elmengardo said:
Same problem for me, did you solved it?
Click to expand...
Click to collapse
at that point try this command: fastboot boot recovery.img
it worked for me

does it work in Asus Zenfone Selfie ZD551KL Z00UD android 6.0.1?

fastboot oem reboot -recovery faild how i solve it ?
C:\Users\acer\Desktop\New folder\asus_zenfone_selfie_recovery_toolkit>fastboot oem reboot -recovery
...
FAILED (remote: unknown command)
finished. total time: 0.002s
how to resolve my phone is asus zenfone selfie
android version : 6.0.1
how i solve it ?

Hiroyt01 said:
Hi everyone !
So I tryed to install CM on my Asus zenfone (Z00UD) and everything worked with no problems until the fastboo oem reboot-recovery.
So I tryed to reboot while pressing the VOLUME DOWN key and i get to the original recovery mode.
My phone is still booting to the usual android when I boot without going in recovery.
So I guess TWRP flash didn't worked as excepted, but i remember it showing completed.
Is there a way to verify that TWRP isn't installed so i can re install it ?
Or is it another problem ?
Click to expand...
Click to collapse
I have the same phone Hiroyte but I cant unlock bootloader because the system does not boot to OS >> any help to do this without boot into the system ?
thanks

Pixel C - fastboot unsupported command

Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !

Did you unlock your device first with "fastboot oem unlock"?

redukt said:
Did you unlock your device first with "fastboot oem unlock"?
Click to expand...
Click to collapse
Yes i did this before, i was running on Remix OS

I don't know if this is of relevance but there were new fastboot commands introduced from Android M (?) and I have recollection about "partial unlock" - two flags required to be set and if only one was set it could be reported that the bootloader was unlocked but fastboot saw it as locked. Above may be totally wrong.
Here's the difference between old and current fastboot commands. Note the new lock/unlock commands
Code:
************************ OLD **************************************
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
************************ NEW **************************************
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.

-Yazh- said:
Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !
Click to expand...
Click to collapse
Hi, I'm just wondering if you were able to fix your tablet. I ran into the same problem as you here and am not able to find a solution to it.

Hi !!
Sorry for bad news, but i didn't found any solution since my Pixel C was bricked. Maybe there is a solution, but I dropped it before finding it.
I hope you find something to fix it !

@viii_xvi Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html

peterk-1 said:
Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
Click to expand...
Click to collapse
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
peterk-1 said:
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?

viii_xvi said:
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?
Click to expand...
Click to collapse
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.

peterk-1 said:
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.
Click to expand...
Click to collapse
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
fastboot: usage: no command
Click to expand...
Click to collapse

viii_xvi said:
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
Click to expand...
Click to collapse
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.

rhmanoa said:
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.
Click to expand...
Click to collapse
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.

viii_xvi said:
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.
Click to expand...
Click to collapse
Just bought today, same issue, have you solved it?

mansonstein said:
Just bought today, same issue, have you solved it?
Click to expand...
Click to collapse
No, I didn't manage to fix it.

did you found a solution yet？
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command

richardwia said:
did you found a solution yet？
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command
Click to expand...
Click to collapse
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.

viii_xvi said:
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.
Click to expand...
Click to collapse
really？where I can find the“fix fastboot in advanced options”？

richardwia said:
really？where I can find the“fix fastboot in advanced options”？
Click to expand...
Click to collapse
I believe I'm not qualified to help you as I disposed of my tablet months ago. All the advice I've given is off of memory and may not be accurate. That being said, I won't help you anymore in fear of giving inaccurate information that may lead to bricking of your tablet.

I have a pixel C, flashed with latest 3-rd pixel experience before, someday i tried to flash back to factory image, hit the same trouble like this topic, i came here several times before, no solution, today, i found another article about this , it's solved my trouble.
sorry i am new here, i couldn't share the outside article link.
would like to share what i did on my pixel c.
1. root your pixel c
2. adb shell //this command could be executed under recovery mode too.
3. su
4. fwtool vbnv write dev_boot_fastboot_full_cap 1
5. adb reboot fastboot
then you could flash anything you want.

I had this just now - I finally got fed up of my Pixel C being so laggy and also chrome opening up as blank pages (I switched to brace to fix this, but it's abit crashy).
Anyhow I found that after
adb reboot bootloader
that
fastboot flash recovery twrp.img
was failing for me in the "Writing" stage
I discovered that the fix was to use
adb flashing unlock
then it will ask you a question (power button to confirm and one of teh volume keys to cancel).
after this it spins with erasing for a while and then comes back to fastboot after which
fastboot flash recovery twrp.img
Worked, after this you get an annoying 30s delay for each restart, I think that can be fixed by
adb flashing lock
I'll verify this when I've finished flashing a usable ROM to my Pixel C...

FAILED (remote: Command not allowed)

Hi, I am trying to install twrp twrp-3.1.1-0-odin.img so I can get RR rom on my C6502
first of all, I'm well aware of steps, and I personally have this rom installed in my xperia m, so it won't be hard for me to understand and it's quite easy as 123 over there
the problem I'm facing is, this xperia ZL c6502 l35h device seems to have something in different I'm not able to flash twrp here
I used repair feature in sony pc companion, done successfully, start device, wait for first boot time, configure, enable unknown source, enable usb debugging, connect cable to pc and allow RSA pc's code
power off and connect with voldown, used flash tool to unlock bootloader (yes the blootloader status unlock is yes in *#*#7378042#*#* code confi thing)
bootloader unlocked successfully, device tried to be in bootloop for three times, then it started, like first boot took somewhere 15 min to start up, and everything is fine, except I cannot increase brightness anymore but nvm
I again enable unknown source, and usb debugging, and allow my pc's RSA key > always allow
poweroff, connect in fastboot, flash kernel > select the just downloaded twrp from official source 3.1.1.0 I think
I flash receive an error says remote: command not allowed
22/002/2017 07:02:33 - INFO - Device connected in fastboot mode
22/002/2017 07:02:39 - INFO - Selected kernel (boot.img or kernel.sin): D:\IDM\General\twrp-3.1.0-0-odin.img
22/002/2017 07:02:39 - INFO - Flashing selected kernel
22/002/2017 07:02:40 - INFO - sending 'boot' (11406 KB)...
22/002/2017 07:02:40 - INFO - OKAY [ 0.361s]
22/002/2017 07:02:40 - INFO - writing 'boot'...
22/002/2017 07:02:40 - INFO - FAILED (remote: Command not allowed)
22/002/2017 07:02:40 - INFO - finished. total time: 0.363s
22/002/2017 07:02:40 - INFO - FASTBOOT Output:
sending 'boot' (11406 KB)...
OKAY [ 0.361s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.363s
tried to used minimal adb and fast boot
here's the log
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (11474 KB)...
OKAY [ 0.364s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.368s
So, I have my bootloader unlocked, I can confirm that because after booting up post unlock, there's change in system, I cannot increase brightness, and in that code *#*#7378... I see more Bands available before unlock
and device booted after like 3 bootloops automatically, what am I doing wrong, and what should I do? how are people able to get this rom in their device?
btw, I'm dealing with firmware 10.7.A.0.222 India version, all latest as per pc companion repair feature and today it will be offc latest one
and the version of my flashtool is 0.9.18.6
in minimal adb and fastboot, I tried this
fastboot.exe -i 0x0fce getvar version
result is 0.5
fastboot.exe -i 0x0fce oem unlock 0x[my key in caps]
first time it fails and second time it does, and output is successfull
then I proceed to flash twrp
fastboot flash recovery twrp.img
I receive failed command not allowed
then I try
fastboot flash boot boot.img
successful, but phone bricked
I reflash 10.7.A.0.222 and device working again, but how do I flash twrp?
what am I doing wrong?

Godlydevils said:
Hi, I am trying to install twrp twrp-3.1.1-0-odin.img so I can get RR rom on my C6502
first of all, I'm well aware of steps, and I personally have this rom installed in my xperia m, so it won't be hard for me to understand and it's quite easy as 123 over there
the problem I'm facing is, this xperia ZL c6502 l35h device seems to have something in different I'm not able to flash twrp here
I used repair feature in sony pc companion, done successfully, start device, wait for first boot time, configure, enable unknown source, enable usb debugging, connect cable to pc and allow RSA pc's code
power off and connect with voldown, used flash tool to unlock bootloader (yes the blootloader status unlock is yes in *#*#7378042#*#* code confi thing)
bootloader unlocked successfully, device tried to be in bootloop for three times, then it started, like first boot took somewhere 15 min to start up, and everything is fine, except I cannot increase brightness anymore but nvm
I again enable unknown source, and usb debugging, and allow my pc's RSA key > always allow
poweroff, connect in fastboot, flash kernel > select the just downloaded twrp from official source 3.1.1.0 I think
I flash receive an error says remote: command not allowed
22/002/2017 07:02:33 - INFO - Device connected in fastboot mode
22/002/2017 07:02:39 - INFO - Selected kernel (boot.img or kernel.sin): D:\IDM\General\twrp-3.1.0-0-odin.img
22/002/2017 07:02:39 - INFO - Flashing selected kernel
22/002/2017 07:02:40 - INFO - sending 'boot' (11406 KB)...
22/002/2017 07:02:40 - INFO - OKAY [ 0.361s]
22/002/2017 07:02:40 - INFO - writing 'boot'...
22/002/2017 07:02:40 - INFO - FAILED (remote: Command not allowed)
22/002/2017 07:02:40 - INFO - finished. total time: 0.363s
22/002/2017 07:02:40 - INFO - FASTBOOT Output:
sending 'boot' (11406 KB)...
OKAY [ 0.361s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.363s
tried to used minimal adb and fast boot
here's the log
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (11474 KB)...
OKAY [ 0.364s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.368s
So, I have my bootloader unlocked, I can confirm that because after booting up post unlock, there's change in system, I cannot increase brightness, and in that code *#*#7378... I see more Bands available before unlock
and device booted after like 3 bootloops automatically, what am I doing wrong, and what should I do? how are people able to get this rom in their device?
btw, I'm dealing with firmware 10.7.A.0.222 India version, all latest as per pc companion repair feature and today it will be offc latest one
and the version of my flashtool is 0.9.18.6
in minimal adb and fastboot, I tried this
fastboot.exe -i 0x0fce getvar version
result is 0.5
fastboot.exe -i 0x0fce oem unlock 0x[my key in caps]
first time it fails and second time it does, and output is successfull
then I proceed to flash twrp
fastboot flash recovery twrp.img
I receive failed command not allowed
then I try
fastboot flash boot boot.img
successful, but phone bricked
I reflash 10.7.A.0.222 and device working again, but how do I flash twrp?
what am I doing wrong?
Click to expand...
Click to collapse
Just to confirm that you did change your downloaded recovery name to boot.img and placed it inside c drive adb folder, right?

hhjadeja007 said:
Just to confirm that you did change your downloaded recovery name to boot.img and placed it inside c drive adb folder, right?
Click to expand...
Click to collapse
yes, I renamed to boot.img after googling and learning,
and as I had minimal adb and fastboot installed in
C:\Program Files (x86)\Minimal ADB and Fastboot
I placed in that directory
is that correct?

Godlydevils said:
yes, I renamed to boot.img after googling and learning,
and as I had minimal adb and fastboot installed in
C:\Program Files (x86)\Minimal ADB and Fastboot
I placed in that directory
is that correct?
Click to expand...
Click to collapse
Yeah that's correct.

hhjadeja007 said:
Yeah that's correct.
Click to expand...
Click to collapse
Hi, I just managed to get it done, but another problem arise
I flash anew 10.7.A.0.222
after that, I ticked unknown source, and enable debugging, and as people mentioned that it means bootloader is not unlocked
I fired this command five times
fastboot.exe -i 0x0fce oem unlock 0xDB29CBBEFBAB4A64
and after that I fired
fastboot flash boot boot.img
output was
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (11474 KB)...
OKAY [ 0.364s]
writing 'boot'...
OKAY [ 0.548s]
finished. total time: 0.915s
means it worked, but when I hold power button, it vibrates, if I press and hold again, it would vibrate, and never start up
if I connect it for charging red LED would blink

Godlydevils said:
Hi, I just managed to get it done, but another problem arise
I flash anew 10.7.A.0.222
after that, I ticked unknown source, and enable debugging, and as people mentioned that it means bootloader is not unlocked
I fired this command five times
fastboot.exe -i 0x0fce oem unlock 0xDB29CBBEFBAB4A64
and after that I fired
fastboot flash boot boot.img
output was
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (11474 KB)...
OKAY [ 0.364s]
writing 'boot'...
OKAY [ 0.548s]
finished. total time: 0.915s
means it worked, but when I hold power button, it vibrates, if I press and hold again, it would vibrate, and never start up
if I connect it for charging red LED would blink
Click to expand...
Click to collapse
Well, it's strange.

hhjadeja007 said:
Well, it's strange.
Click to expand...
Click to collapse
that's the one I'm trying
downloaded from
https://dl.twrp.me/odin/twrp-3.1.1-0-odin.img
okay, I just flashed again .222 I will now unlock bootloader, then restart and post result

Godlydevils said:
that's the one I'm trying
downloaded from
https://dl.twrp.me/odin/twrp-3.1.1-0-odin.img
okay, I just flashed again .222 I will now unlock bootloader, then restart and post result
Click to expand...
Click to collapse
Maybe try pressing vol + button just like Xperia m after mobile vibrates

hhjadeja007 said:
Maybe try pressing vol + button just like Xperia m after mobile vibrates
Click to expand...
Click to collapse
Here's something more I learned
If you unlock boot loader, and restart, > tick unknown + usb debugging, and boot to bootloader, it won't let you flash boot.img
but if you immediately unlock bootloader, and without restart, you flash boot.img, it will go success
but after that, your device won't start
it's not starting, it vibrates, but no display, no matter how many times you press and hold power button to start it, it will vibrate, and won't start
I tried each and every combination of vol +/- and power button, but it's not starting that way
EDIT:
but I can still press and hold vol up and connect cable to get in fastboot mode, after which if I try flashing twrp, i again get command not allowed, except if I try fastboot.exe -i 0x0fce oem unlock 0xDB29CBBEFBAB4A64 and then fastboot flash boot boot.img
after which I will get success flashing that recovery, but device won't start

Godlydevils said:
Here's something more I learned
If you unlock boot loader, and restart, > tick unknown + usb debugging, and boot to bootloader, it won't let you flash boot.img
but if you immediately unlock bootloader, and without restart, you flash boot.img, it will go success
but after that, your device won't start
it's not starting, it vibrates, but no display, no matter how many times you press and hold power button to start it, it will vibrate, and won't start
I tried each and every combination of vol +/- and power button, but it's not starting that way
EDIT:
but I can still press and hold vol up and connect cable to get in fastboot mode, after which if I try flashing twrp, i again get command not allowed, except if I try fastboot.exe -i 0x0fce oem unlock 0xDB29CBBEFBAB4A64 and then fastboot flash boot boot.img
after which I will get success flashing that recovery, but device won't start
Click to expand...
Click to collapse
For me, i think if you're recently to unlock your bootloader. Have you try to confirmed that your bootloader really unlocked from stock firmware? (*#*#7378423#*#*) and see about bootloader info?
If bootloader already unlocked, then you're safe to flash, And have you read any requirement to flash recovery for your device? i think it's like only work for custom rom or only work for specified version of firmware?
If device won't start, then it should from kernel problem. Try to check your custom recovery compatibility before flashing, and tell us what happen next

Nicklas Van Dam said:
For me, i think if you're recently to unlock your bootloader. Have you try to confirmed that your bootloader really unlocked from stock firmware? (*#*#7378423#*#*) and see about bootloader info?
If bootloader already unlocked, then you're safe to flash, And have you read any requirement to flash recovery for your device? i think it's like only work for custom rom or only work for specified version of firmware?
If device won't start, then it should from kernel problem. Try to check your custom recovery compatibility before flashing, and tell us what happen next
Click to expand...
Click to collapse
okay,
so few points worth mentioning
1) my bootloader is unlockable, and is unlocked, I mean in 7378423 it's written yes in root status bl unlock
2) I have received code from sony, and I can unlock it
3) the only recovery that works is https://forum.xda-developers.com/showthread.php?t=2288118 that too only after using kingroot, which gives me old philz and 2.8.7.0 twrp which are not helpful, also I tried to flash RR 7.1.2 based, phone basically gets bricked
4) I can only flash twrp or any recovery if I unlock bootloader, and without restarting I flash boot.img, if I do so, phone gets bricked
Here's the ss of BL status
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There's nothing written about requirements of twrp to flash, or rom, they just don't have, but as I have latest firmware, it should work, even nothing is written in linageos thread

I found basically few members of the community faced this problem
https://forum.xda-developers.com/xperia-zl/help/related-problems-flashing-stock-t3274520/

Godlydevils said:
okay,
so few points worth mentioning
1) my bootloader is unlockable, and is unlocked, I mean in 7378423 it's written yes in root status bl unlock
2) I have received code from sony, and I can unlock it
3) the only recovery that works is https://forum.xda-developers.com/showthread.php?t=2288118 that too only after using kingroot, which gives me old philz and 2.8.7.0 twrp which are not helpful, also I tried to flash RR 7.1.2 based, phone basically gets bricked
4) I can only flash twrp or any recovery if I unlock bootloader, and without restarting I flash boot.img, if I do so, phone gets bricked
Here's the ss of BL status
There's nothing written about requirements of twrp to flash, or rom, they just don't have, but as I have latest firmware, it should work, even nothing is written in linageos thread
Click to expand...
Click to collapse
Man Your bootloader is locked. It can be clearly seen from screen shot

hhjadeja007 said:
Man Your bootloader is locked. It can be clearly seen from screen shot
Click to expand...
Click to collapse
can you explain?

hhjadeja007 said:
Man Your bootloader is locked. It can be clearly seen from screen shot
Click to expand...
Click to collapse
Better?

Godlydevils said:
Better?
Click to expand...
Click to collapse
Yeah now you are good to go

hhjadeja007 said:
Yeah now you are good to go
Click to expand...
Click to collapse
so far, I am able to flash twrp, and I just flashed RR with gapps and mod, just got into settings wizard, will update/comment if I face any problem other than music has stopped working :/

Godlydevils said:
so far, I am able to flash twrp, and I just flashed RR with gapps and mod, just got into settings wizard, will update/comment if I face any problem other than music has stopped working :/
Click to expand...
Click to collapse
Okay, that's good. Now my questions , that is recovery based on FOTA or only normal recovery based on Boot.IMG?
Sent from my nicki using XDA Labs

Nicklas Van Dam said:
Okay, that's good. Now my questions , that is recovery based on FOTA or only normal recovery based on Boot.IMG?
Sent from my nicki using XDA Labs
Click to expand...
Click to collapse
boot.img
The problem was with the lolipop rom
Had to flash Kitkat, and unlock bootloader, no probs

Hello
my name is modou sow.in fact i have a problem with my huawei p9 lite.je wanted to put on my my phone and i did a wrong handling and because it could not walk any more.auauf mode wipe / data which ended in failure. Then I tried to install the recovery, boot, system ... but at any time I have the results:
*FAILED (remote: Command not allowed);
please help me;
I apologize for the bad English because I am Senegalese.

Root? Roms? Custom Recovery? Bootlocker Unlock? Anyone?

Someone needs to start this. I can't believe no one has yet looked at this. Tell me someone has achieved some of this please.

GodKingKnight said:
Someone needs to start this. I can't believe no one has yet looked at this. Tell me someone has achieved some of this please.
Click to expand...
Click to collapse
I also was wondering everytime i came to this forum, why no developer yet did not showup here. Is asus not devs friendly.. i am planning to buy it but only after i will see some hope of custom rom development.

nadeem_naddy said:
I also was wondering everytime i came to this forum, why no developer yet did not showup here. Is asus not devs friendly.. i am planning to buy it but only after i will see some hope of custom rom development.
Click to expand...
Click to collapse
I am also checking 5z forums daily
Asus have launched kernel sources and it is project treble supported and custom rom development is easy so looking forward for some development to start:crying::crying::crying:

i was planning to buy this phone as i wanted to flash resurrection remix but guess have to wait

The phone released recently, and very late in the year. Most devs are on treble phones, or ones like the OnePlus 6. The phone is probably treble compliant, so in theory owners can use any treble ROM.

TWRP to ZS620KL (snapdragon 845, 8/256GB)
I am looking for TWRP to ZS620KL (snapdragon 845, 8/256GB) can anyone help me? It does not work for ZE620KL, unfortunately. I need a good TWRP urgently.

jakubdg said:
I am looking for TWRP to ZS620KL (snapdragon 845, 8/256GB) can anyone help me? It does not work for ZE620KL, unfortunately. I need a good TWRP urgently.
Click to expand...
Click to collapse
Have you unlocked the bootloader ??
is it same as zenfone 5 2018
If yes then share the method

Akash1998 said:
Have you unlocked the bootloader ??
is it same as zenfone 5 2018
If yes then share the method
Click to expand...
Click to collapse
Yes I have unlocked bootloader. I used official asus apk
Then downloaded twrp-3.2.1-0-X00Q-20180508.img
Next fastboot flash boot recovery.img and fastboot flash recovery recovery.img - I saw Bootloader Version is empty
Now I dont know how I have older bootloader version WW_user_80.11.37.53 but I do not have twrp.

Edit: Please use my updated guide:
https://forum.xda-developers.com/zenfone-5z/how-to/guide-zenfone-5z-how-to-root-downgrade-t3815877
Here is what i did to root the 5Z ZS620KL:
1. Download the unlock app AND the installed firmware from asus:
download
2. Install adb and fastboot
download
3. Copy the app to the phone, start it and follow the on screen instructions > bootloader unlocked
Warning: When booting the phone you will now see a warning message!
4. Unzip the downloaded firmware and use a tool to extract the boot.img from the payload.bin. I used payload_dumper.
download
5. Copy the extracted boot.img from payload_output folder to the 5z.
6. Download magisk manager app from the officiall thread on xda, install it and use it to patch the boot.img on your phone (install>install>patch boot.img)
download
7. Copy the patched_boot.img back to your computer (the original boot.img will be approx 65mb the patched one approx 19mb)
8. Start your phone in fasboot mode (hold "power + volume up" to switch on your phone). You will see "FastBoot Mode" in red letters on screen. Connect your phone to the computer using the usb cable.
9. Open a command line and check if your phone is recognized by executing:
Code:
fastboot devices
You should see the serial number of your phone.
10. Change to the path where you copied your patched_boot.img and use fastboot to flash the patched_boot.img to your device:
Code:
fastboot flash boot patched_boot.img
11. Start your phone from the fastboot menu using volume up/down and power to select.
Bugs/problems:
- You will see three warning messages while booting, at least i do. One for the unlocked bootloader and the next one comes twice saying "There is an internal problem with your device. Contact your manufacturer for details." which you have to confirm.
- I used the latest stable Magisk V16.0 + Manager V5.8 and Magisk hide is not working. It does not save the apps marked for hide. Maybe some write error?

I have purchased zenfone 5Z but it's model number on box is ZS621KL. I see the guide posted for rooting and TWRP install is for ZS620KL. is this same guide applicable to my model as well or this is a different version something like zenfone 5 and Not zenfone 5 Z

isthisadagger said:
Here is what i did to root the 5Z ZS620KL:
1. Download the unlock app AND the installed firmware from asus:
download
2. Install adb and fastboot
download
3. Copy the app to the phone, start it and follow the on screen instructions > bootloader unlocked
Warning: When booting the phone you will now see a warning message!
4. Unzip the downloaded firmware and use a tool to extract the boot.img from the payload.bin. I used payload_dumper.
download
5. Copy the extracted boot.img from payload_output folder to the 5z.
6. Download magisk manager app from the officiall thread on xda, install it and use it to patch the boot.img on your phone (install>install>patch boot.img)
download
7. Copy the patched_boot.img back to your computer (the original boot.img will be approx 65mb the patched one approx 19mb)
8. Start your phone in fasboot mode (hold "power + volume up" to switch on your phone). You will see "FastBoot Mode" in red letters on screen. Connect your phone to the computer using the usb cable.
9. Open a command line and check if your phone is recognized by executing:
Code:
fastboot devices
You should see the serial number of your phone.
10. Change to the path where you copied your patched_boot.img and use fastboot to flash the patched_boot.img to your device:
Code:
fastboot flash boot patched_boot.img
11. Start your phone from the fastboot menu using volume up/down and power to select.
Bugs/problems:
- You will see three warning messages while booting, at least i do. One for the unlocked bootloader and the next one comes twice saying "There is an internal problem with your device. Contact your manufacturer for details." which you have to confirm.
- I used the latest stable Magisk V16.0 + Manager V5.8 and Magisk hide is not working. It does not save the apps marked for hide. Maybe some write error?
Click to expand...
Click to collapse
where can I find payload.bin ?
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
where can I find payload.bin?
---------- Post added at 06:29 PM ---------- Previous post was at 06:08 PM ----------
where can I find payload.bin ?

I need help...
when I try upload twrp twrp-3.2.1-0-X00Q-20180508.img
(SK620KL snap845 8/256GB unlocked)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp-3.2.1-0-X00Q-20180508.img
target reported max download size of 268435456 bytes
sending 'boot' (25244 KB)...
OKAY [ 0.552s]
writing 'boot'...
OKAY [ 0.103s]
finished. total time: 0.658s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-X00Q-20180508.img
target reported max download size of 268435456 bytes
sending 'recovery' (25244 KB)...
OKAY [ 0.557s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.570s
then in Fastboot Mode I have: BOOTLOADER VERSION - Error
the phone does not start ((
maybe other recovery.img??

When and where you have find a TWRP recovery for ZenFone 5 z (SK620KL) ??????!!!!!!!!!!!?????????
Reflash stock recovery if you can but you flash wrong TWRP for your model of your device ..... You soft brick or hard brick your device
Before READ the tutorial step by step and watch the model of the device ............ It's the base for an hacker
You have ZenFone 5 z with stock rom like pixel rom with the snp 845 what do you need ? why you want install TWRP no custom rom at this moment just trebble project but it's not for now the best way
And ZenFone 5 received Android P just wait

jakubdg said:
I need help...
when I try upload twrp twrp-3.2.1-0-X00Q-20180508.img
(SK620KL snap845 8/256GB unlocked)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp-3.2.1-0-X00Q-20180508.img
target reported max download size of 268435456 bytes
sending 'boot' (25244 KB)...
OKAY [ 0.552s]
writing 'boot'...
OKAY [ 0.103s]
finished. total time: 0.658s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-X00Q-20180508.img
target reported max download size of 268435456 bytes
sending 'recovery' (25244 KB)...
OKAY [ 0.557s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.570s
then in Fastboot Mode I have: BOOTLOADER VERSION - Error
the phone does not start ((
maybe other recovery.img??
Click to expand...
Click to collapse
If your computer is able to use fastboot.exe.
Please try
Download WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release.zip
Extract this zip file.
Connect your 5Z with your computer.
Start cmd, and move into path to folder (WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release) .
Type `flashall_AFT.cmd`.

amanfdk said:
I have purchased zenfone 5Z but it's model number on box is ZS621KL. I see the guide posted for rooting and TWRP install is for ZS620KL. is this same guide applicable to my model as well or this is a different version something like zenfone 5 and Not zenfone 5 Z
Click to expand...
Click to collapse
Go to system>about phone> sofware version and check your version. Mine starts with WW_80.11.37.69. You need to download the right firmware version from asus (WW or JP). It should work for ZS621KL.

isthisadagger said:
Go to system>about phone> sofware version and check your version. Mine starts with WW_80.11.37.69. You need to download the right firmware version from asus (WW or JP). It should work for ZS621KL.
Click to expand...
Click to collapse
Mine is also similar. So have you tried this guide is our working for you.

Renaf2 said:
When and where you have find a TWRP recovery for ZenFone 5 z (SK620KL) ??????!!!!!!!!!!!?????????
Reflash stock recovery if you can but you flash wrong TWRP for your model of your device ..... You soft brick or hard brick your device
Before READ the tutorial step by step and watch the model of the device ............ It's the base for an hacker
You have ZenFone 5 z with stock rom like pixel rom with the snp 845 what do you need ? why you want install TWRP no custom rom at this moment just trebble project but it's not for now the best way
And ZenFone 5 received Android P just wait
Click to expand...
Click to collapse
I wanted to install twrp + root + adaway or other adblock nothing more... I used this info getdroidtips.com/root-twrp-recovery-asus-zenfone-5z
Now I have problem, 5Z still rebooting when I go to recovery or bootloader or start system
---------- Post added at 11:54 AM ---------- Previous post was at 11:27 AM ----------
GSPD said:
If your computer is able to use fastboot.exe.
Please try
Download WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release.zip
Extract this zip file.
Connect your 5Z with your computer.
Start cmd, and move into path to folder (WW__ZS620KL_80.10.8.54_MP_user_20180517175955_release) .
Type `flashall_AFT.cmd`.
Click to expand...
Click to collapse
It works!!! Thank you very much! )
How can I install twrp, root? I want to run adaway or adblock

I have another question, now I have version ww_user_80.10.8.54 I would like to have new version WW-80.11.37.86. How can I install? OTA not work, how can I install zip file from asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_BIOS ? I would like to have a new version with twrp/root

jakubdg said:
I have another question, now I have version ww_user_80.10.8.54 I would like to have new version WW-80.11.37.86. How can I install? OTA not work, how can I install zip file from asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_BIOS ? I would like to have a new version with twrp/root
Click to expand...
Click to collapse
Talking about the steps what I have done for update my 5z.
Put the zip file that you downloaded on /sdcard/
And reboot.
After these steps, the device will find the update and let you to operate to update.
Please try .

GSPD said:
Talking about the steps what I have done for update my 5z.
Put the zip file that you downloaded on /sdcard/
And reboot.
After these steps, the device will find the update and let you to operate to update.
Please try .
Click to expand...
Click to collapse
It works! Super, I have WW-80.11.37.86
How can I install twrp and root?