Database Users

[Q] Fastboot?

Ive modified the android_winusb.inf to show the correct device ID 0FCE for windows 7 x64 installed it and thats gone fine.
Now trying devices gives me nothing reboot-bootloader gives me <waiting for device> cant make a decent boot.img backup to inject Root, anyone got any ideas how we can connect fastboot, the bootloader is unlocked but unconfirmed.
Until we can get a decent boot.img we cant really start the development.
fastboot.exe -i 0x0fce getvar version connects and displays fine.

are you starting your phone in bootloader mode?
power off
hold <search> + plug into usb
I was able to issue fastboot commands from there such as fastboot reboot. If your bootloader is unlocked you should be able to use any of the below commands. You can also modify the boot.img from the recovery image from the bundled software. And boot to it on sd without writing to nand.
I've been pretty busy or else I'd try it myself, I just played with it enough to unlock my bootloader myself and that's where I stopped. If you need some help let me know.
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
EDIT: if you are having issues with "fastboot devices" and you are entering bootloader correctly, you may need to restart your workstation

Yeah done all that im sure the bootloader is now unlocked it erased the blocks and reset my phone, ill boot into ubuntu and try it from there. Windows wont let me issue any commands
Sent from my R800i using XDA Premium App. the keyboard auto correct function is mental it changes all my words got to turn that off

waz000000 said:
Yeah done all that in sure the overloaded is now unlocked it erased the blocks and reset my phone, ill boot into ubuntu and try it from there. Windows wont let me issue any commands
Sent from my R800i using XDA Premium App
Click to expand...
Click to collapse
I tried downloading the "repair" image and it sees that we modified the bootloader and won't download the image and the only files on SE website is for the update software not the image which I think is kinda bullsh*t but whatever.
so... if someone that *HAS NOT* unlocked the bootloader can download and mirror the file it downloads, should 100+ mb somewhere on your computer possibly in your %temp% directory if you are on a windows based workstation

I had the same problem cant restore major over sight by sony if our software breaks any time soon....
We need the unmodified boot.img only problem is i have another play ones got to go back that one is fresh in the packet but with the bootloader locked we cant issue commands with fast boot. catch 22
Sent from my GT-P1000 using XDA Premium App

waz000000 said:
I had the same problem cant restore major over sight by sony if our software breaks any time soon....
We need the unmodified boot.img only problem is i have another play ones got to go back that one is fresh in the packet but with the bootloader locked we cant issue commands with fast boot. catch 22
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
also the /proc/mtd for the boot partition is hidden in case anyone suggests we just pull for a backup.
Another reason I won't be doing much tinkering untill someone can provide us with a recovery image (note not just /system dump)

[GUIDE][Osprey] Fastboot Flashing Factory Firmware Images

Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own.​
Based on existing tutorial by @t-bon3. This guide has been created as a hard-brick occurred using the old Moto G (1st Gen) tutorial. Please exercise extreme care with Fastboot, and only use the commands mentioned here. Experimenting with Fastboot commands can seriously damage your phone.
How to Fastboot Flash Moto G (3rd Gen) Factory Firmware Images​
Required Files:
Motorola Drivers: Download
Latest Fastboot | ADB (Windows | Linux): Download (Windows 10 users may need this pack for Drivers to work.)
Factory Firmware Images: [INDEX][Osprey] Moto G Factory Firmware Images​
WARNING: You must perform a 'Factory data reset' in Stock Recovery before flashing any Firmware Image - instructions here.​
Instructions:
1) Extracting Fastboot and Firmware Images:
Extract zip for chosen Firmware Image to a folder with a simple directory structure. For example: C:\motog_firmware\
Extract the adb-fastboot-latest_win_linux.zip into this folder.​
2) Reboot the phone into 'Bootloader mode' and preparing PC for flashing
Windows:
Entering Fastboot mode:
------------------------------------
i) The 'hardware' way.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.
ii) The 'software' way.
a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
d) Open Command Prompt, navigate to the Firmware / ADB folder (i.e CD C:\motog_firmware ) and type:
Code:
adb reboot-bootloader
Linux:
Entering Fastboot mode:
------------------------------------
i) The 'hardware' way.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.
ii) The 'software' way. (Requires ADB to be already installed - see below)
a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB
d) Navigate to the Firmware folder, right-click and open terminal and type:
Code:
adb reboot-bootloader
Installing ADB / Fastboot:
-------------------------------------
Flashing via Linux LiveCD: (Put factory firmware files on an external usb drive / pen)
--------------------------------
a) Download Ubuntu LiveCD
b) Burn to DVD or write to USB pen
c) Restart PC, Boot from DVD into Ubuntu
d) Open Terminal and type the following:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot​
e) Test fastboot by typing: sudo fastboot devices
You should see:
<serial number> fastboot​f) You are now ready to flash the fastboot files
​
3) Fastboot Commands:
Do commands manually, one at a time - checking that each one returns an [OKAY].​
NOTE: Do not simply copy and paste these commands! - system.img_sparsechunks may differ in number and name.
Always check contents of folder you're working with. You must flash all of the sparsechunk files you have.​
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot​
ALWAYS CHECK YOUR MODEL
FLASHING WRONG FIRMWARE CAN DESTROY A PHONE​

Frequently Asked Questions:
Can I restore Factory Firmware if my Bootloader is locked?
Yes. However attempting to downgrade to an older version of Android may fail - 'Preflash validation' error. Even with an unlocked Bootloader, downgrading cannot be guaranteed. It's also important to be aware that flashing the wrong Bootloader (bootloader.img) for your model can have serious consequences. Always establish your model of Moto G before flashing.
I get a 'Preflash validation' error when flashing a Firmware Image
The Firmware Image you are trying to flash is too old. You can only flash a firmware image that matches, or is newer than the most recent system version you have had on your phone. However the former scenario can also sometimes return the error. In which case, your options are to wait for an even newer firmware image or unlock Bootloader and flash a ROM zip.
After flashing Firmware Image files phone gets stuck during boot-up | will not load Android?
Check you are naming the files correctly, and make sure you are flashing all of the 'sparsechunk' files - not just those mentioned in the tutorial. The 'sparsechunk' commands listed there are not to be copied exactly, different firmware images may have different files.
How to flash Radio Firmware only?
Use the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn​
How do I downgrade to an older Firmware?
Downgrading carries risks, and may result in constant nagging notifications to update Android. Decide carefully if this is really what you want. With earlier generations of Moto G flashing bootloader.img and gpt.bin has resulted in a hard-brick. Avoid flashing these files if you are trying to downgrade. The safer option is to find a custom Stock ROM with OTA Updates disabled.
Fastboot in Linux is not working?
In Linux, root access is required for Fastboot and/or ADB to work.
sudo fastboot devices​

Hi @lost101
Need a clarification in the 3rd point (fastboot commands),
Whether it's
fastboot flash bootloader bootloader.img
OR
fastboot flash motoboot bootloader.img

==vj== said:
Hi @lost101
Need a clarification in the 3rd point (fastboot commands),
<snip>
Click to expand...
Click to collapse
From the Firmware Images I've checked; the file is called: bootloader.img and the partition: bootloader
EDIT: This information is based on the servicefile.xml included with many of these firmware images.

Hey im new here and with rooting
i recently rooted my phone but now when i try to start up the screen goes black.
im downloading the file now can someone tell my how to flash the firmware succesfully?
model: xt1541 moto g 2015
pleas reply thanks

Help to change my firmaware
Dear Lost101,
First at all, thanks for your post.
I was trying to change the firmware of my phone, because I live in Argentina and use a different band for 4G LTE Spain (where I bought the phone).
My Moto G3 is XT1541, and I need the XT1540.
When I was changing the firmare, I had problems when I wrote "fastboot flash boot boot.img"... The command shows "FAILED". Then, I change the model, put again the firmare XT1541, and everything will be right again.
Do you know why I couldn't flash with XT1540?
Best regards and thanks in advance!

Demians1 said:
I was trying to change the firmware of my phone, because I live in Argentina and use a different band for 4G LTE Spain (where I bought the phone).
My Moto G3 is XT1541, and I need the XT1540.
When I was changing the firmare, I had problems when I wrote "fastboot flash boot boot.img"... The command shows "FAILED". Then, I change the model, put again the firmare XT1541, and everything will be right again.
Do you know why I couldn't flash with XT1540?
Click to expand...
Click to collapse
Flashing a different Model Firmware will not magically unlock or change Band support. Maybe with an unlocked Bootloader you can flash another Model's Firmware, but proceed with caution as you could end up with a dead phone.

Thanks Lost101.
Really I dont looking for change my firmware, but I suppuose that this could be a way to change the cell band....
Do you know or you heard about some way to change band support?

Demians1 said:
Really I dont looking for change my firmware, but I suppuose that this could be a way to change the cell band....
Do you know or you heard about some way to change band support?
Click to expand...
Click to collapse
There is this guide for Moto G (1st Gen) and this universal guide - however I don't know if either will work for you or what damage trying them might cause.

Thnak you very much Lost101!

just a small tip you can copy all text and flash then paste it in CMD it will flash all the partitions no need to enter manually one by one

Dear all,
I have a XT1541, and flash my Moto G3 with a XT1540 and XT1543 firmwares without problems. However I had to unblock the phone before flash it.
Lost101 I can confirm you that replace the model firmware DO NOT change the band frequencies... Thanks again for your warnings!

Very useful guide. Everything is working fine.

lost101 i have an error wit xt1544
see:
Code:
c:\celular>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing ´partition´...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.432s

douglaswfranciscon said:
lost101 i have an error wit xt1544
see:
Code:
c:\celular>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing ´partition´...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.432s
Click to expand...
Click to collapse
This usually occurs when attempting to Flash a Firmware Image older than the one currently installed. Unlocking Bootloader will often remove this error.
You can normally skip this command and still successfully flash Android.

lost101 said:
This usually occurs when attempting to Flash a Firmware Image older than the one currently installed. Unlocking Bootloader will often remove this error.
You can normally skip this command and still successfully flash Android.
Click to expand...
Click to collapse
Hello Lost101. I was download de Rom in other Site. The site is a clone for your site, but the rom is diferente.
Today I was downloades the rom in your site and have success...
Thanks!!!
My motoG are live again!

is it possible to just upgrade my phone without wiping everything? if so, what commands are required just to upgrade it?

krsmit0 said:
is it possible to just upgrade my phone without wiping everything? if so, what commands are required just to upgrade it?
Click to expand...
Click to collapse
Skip the following command: fastboot erase userdata

can i skip bootloader and recovery so they dont overright my custom recovery?

krsmit0 said:
can i skip bootloader and recovery so they dont overright my custom recovery?
Click to expand...
Click to collapse
Yes.

Unable to unlock Nexus 6p with Windows PC

I'm trying to unlock my Nexus 6p but am unable to successful unlock it. Steps I have taken:
1) Turned on device and enabled developer options, unlock permissions, and usb debugging
2) Plugged phone into computer and granted permission to computer
3) Booted phone into fastboot and confirmed connection with commands fastboot devices and fastboot reboot-bootloader
4) After the steps above I type fastboot flashing unlock and get a string of options in the command window but nothing happens on the phone (see copy of text options that appear after typing fastboot flashing unlock)
I'm using ADB version 1.0.31 with Windows 10
Is there a newer version of ADB I need to be using? Any tips or ideas would be appreciated as I would like to unlock the bootloader before I set up my phone.
Thanks,
Rick
Android Debug Bridge version 1.0.31
C:\Users\RXXXX\Android_adb>fastboot flashing unlock
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] 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
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
C:\Users\RXXX\Android_adb>

Under Developer options did u enable the option that says, enable bootloader unlock?

Thanks for the response. Yes I did. In fact, I reset the phone and went back in and enabled developer options and allow unlocking again. I still can't get it to unlock the bootloader.

C5Longhorn said:
Thanks for the response. Yes I did. In fact, I reset the phone and went back in and enabled developer options and allow unlocking again. I still can't get it to unlock the bootloader.
Click to expand...
Click to collapse
I went to developer option and selected allow OEM unlocking. Then my fastboot command worked to unlock my bootloader. I know this is not new information but wanted to confirm to you that I did what you did and it worked

I don't know the version numbers but you have to make sure you are using the latest version of fastboot. If you aren't it won't work. When you open the SDK folder open the exe file, I forget exact name but something like SDKmanager.exe, although I know that isn't right. Make sure to update the platform-tools folder and the latest android version. It should work after that.
If not delete any Nexus toolkits you might have downloaded in the past and try again.
Sent from my Nexus 6P using Tapatalk

C5Longhorn said:
Thanks for the response. Yes I did. In fact, I reset the phone and went back in and enabled developer options and allow unlocking again. I still can't get it to unlock the bootloader.
Click to expand...
Click to collapse
Your issue is that your adb/fastboot is out of date and therefore doesn't recognise the "fastboot flashing unlock" command. How did you install it on your PC? If you didn't install it via the Android SDK that's what you need to do, it's the only way to ensure that you're fully up to date. See my guide for details:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Sent from my Nexus 6P

Thanks everyone, I will download the latest SDK.
Sent from my Nexus 7 using Tapatalk

latest adb version is 1.0.32

Just to close this out, it was indeed the version of ADB I was using. After updating, I was able to unlock quickly. Thanks again to everyone, and esp. Heisenberg.
Sent from my Nexus 7 using Tapatalk

[HELP] ADB "Waiting for device"

Hi,
I was on Resurection Rom 7.1.2, but decided to go back to stock today.
I am after wiping caches, data and system from my phone, so I can only access bootloader and twrp.
I have installed mini adb on Win10, and also Clockworm UniversalAdbDriver but none of them seems to work for me. My phone is not visible in devices manager or in adb commands. I can only see "Waiting for device" , adb devices returns nothing.
I am stuck without the phone
Any advice would be most welcome.
Thanks!

Do you have the Motorola usb drivers installed on your PC?

pablo102 said:
Hi,
I was on Resurection Rom 7.1.2, but decided to go back to stock today.
I am after wiping caches, data and system from my phone, so I can only access bootloader and twrp.
I have installed mini adb on Win10, and also Clockworm UniversalAdbDriver but none of them seems to work for me. My phone is not visible in devices manager or in adb commands. I can only see "Waiting for device" , adb devices returns nothing.
I am stuck without the phone
Any advice would be most welcome.
Thanks!
Click to expand...
Click to collapse
ADB isn't available in the bootloader, you have to use fastboot. Try running "fastboot devices"while connected to your PC and in bootloader mode.
Sent from my Moto G (5) Plus using Tapatalk

riggerman0421 said:
ADB isn't available in the bootloader, you have to use fastboot. Try running "fastboot devices"while connected to your PC and in bootloader mode.
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
Tried that, but Moto is not seen by Windows. I had Motorola Device Manager but it did not help.
Actually, in Windows Device Manager, in hidden devices, I can see Mot Composite ADB Interface.
Can I use other's phone sd card and install from there? Do I need to mount it in twrp?

Make sure you only have one instance of ADB/Fastboot installed. If Motorola Device Manager installed the drivers correctly, [I had to use Motorola Mobile Drivers Installation 6.4.0 gui.] then tey
Code:
fastboot devices
Also be sure USB debugging is on in developers option on your phone.

I have found the problem in in cable/usb socket. It's fine for charging, but somehow the cable needs to be pushed more into the port for windows to see the device.
Enjoining Android again
Thanks for all support!

PS C:\> cd adb
PS C:\adb> fastboot devices
ZY224LGV2S fastboot
PS C:\adb> fastboot recovery twrp-3.3.1-0-potter
usage: fastboot [ <option> ] <command>
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
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
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
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> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\adb>
what to do now

bambamishere said:
PS C:\> cd adb
PS C:\adb> fastboot devices
ZY224LGV2S fastboot
PS C:\adb> fastboot recovery twrp-3.3.1-0-potter
usage: fastboot [ <option> ] <command>
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
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
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
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> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\adb>
what to do now
Click to expand...
Click to collapse
What are you trying to do would be my first question?

Wolfcity said:
What are you trying to do would be my first question?
Click to expand...
Click to collapse
Seems trying to flash the recovery, but using wrong the command. It must be fastboot flash recovery twrp.img

riyan65 said:
Seems trying to flash the recovery, but using wrong the command. It must be fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Seems to me like all this happens in ADB mode which has to be (as you mentioned) in fastboot mode.
So @bambamishere:
Bring the device to fastboot (not ADB) mode, type
Code:
fastboot devices
(you should receive a serial number then)
Then type
Code:
fastboot flash recovery "name of recovery.img"
where "name of recovery.img" stands for the real name like twrp.img or however it's named.
Make sure that the image is in your ADB & fastboot folder on your PC.

[HELP] Z00TD/ZE551KL soft-bricked? No recovery mode, no OS, locked bootloader.

Hey guys, I need help with this Asus Zenfone 2 Laser that:
Cannot boot to any OS (asus logo pops up, freezes, and then a blue screen flashes for a really short period, before it powers off, see video here.)
Can't download the unlock app to unlock bootloader
Can't access ADB
Cannot access Recovery mode
Can't "factory reset", apply update over ADB, etc.
Bootloader is locked
Can't flash custom recovery, boot TWRP, or really anything...
See fastboot reference below for more info
Code:
$ fastboot boot twrp-3.7.0_9-0-Z00T.img
Sending 'boot.img' (31066 KB) OKAY [ 0.987s]
Booting FAILED (remote: 'unlock device to use this command')
fastboot: error: Command failed
$ fastboot flash recovery twrp-3.7.0_9-0-Z00T.img
Sending 'recovery' (31066 KB) OKAY [ 0.987s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flash boot boot.img # (Original boot.img from factory image)
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 17980722).
Sending 'boot' (17559 KB) OKAY [ 1.478s]
Writing 'boot' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot oem device-info
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.003s]
Finished. Total time: 0.003s
As someone who has only worked with Google Pixel phones in the past, I'm very frustrated for a few reasons.
Firstly, why the hell is the ONLY WAY to unlock a bootloader through an app that was released in such a clandestine, under-the-table way?
Second, why is the manufacturer gatekeeping the recovery files? The only way I was able to find the stock recovery.img is through a comment on a Reddit post (ironically posted by an ASUS Employee).
Third, I've been scouring the internet for many, many days trying to find any kind of emergency recovery method, but every single tutorial acts on the assumption that the bootloader is unlocked, and that boot.img, recovery.img, etc. can be flashed.
Enough about the frustration. Now let's talk about what I've tried so far.
I tried ASUS Flash Tool (Finding ADB drivers was a whole different fiasco for this device), and came up empty handed, as it doesn't detect the device when in fastboot mode.
I tried using fastboot to flash boot, recovery, system, fastboot, and dnx/ifwi, to no avail.
I tried booting into recovery via `fastboot reboot recovery`, `fastboot reboot-recovery`, `fastboot oem reboot-recovery`, and by holding Vol Down while booting up. They all give the same result, which is just an instant (<1 second) reboot. My best guess is that recovery.img is either missing or badly corrupt, so the bootloader just gives up and exits immediately.
Please help. I don't want an expensive paperweight sitting in my drawer just because of a bootloop that wasn't my fault (seriously this device just bootlooped itself one day, I didn't flash a custom rom, root or anything like that).
Any help is appreciated,
Thanks in advance

you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417

alecxs said:
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
Click to expand...
Click to collapse
Probably a dumb question, but how can I put my device into EDL mode?
I've tried many key combinations in conjunction with plugging it into the computer, and I've tried connecting it without a battery.

if nothing else works you need to figure out test points
https://forum.xda-developers.com/t/...ed-to-unlock-bootloader.4531349/post-87944673

you still have fastboot? try this for EDL mode.
Code:
fastboot oem enter-dload

Good news and bad news. Good news is: I was able to enter EDL mode.
Bad news is, apparently my entire partition scheme was messed up, and upon running "edl w gpt gptboth0.bin", fastboot no longer works.
I have tried flashing aboot using edl ("edl w aboot emmc_appsboot.mbn") and it's not working.
Not to mention that it is almost impossible to find the firmware file with all the factory files such as "emmc_appsboot.mbn". The place where I got my file seemed very sketchy and I'm not surprised if the reason it's not working is because it's the wrong file.
Once again, this is a result of ASUS gatekeeping their recovery files to service centers to drive up repair sales.
If anyone has a link, or would like to provide a donor file, it would be VERY much appreciated.

what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios

alecxs said:
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
Click to expand...
Click to collapse
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...

OS were
sj-dan said:
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
Click to expand...
Click to collapse
So we're you able to find a fix in any way? I find myself in just about the same situation tho for different reasons. I have a radiant max 5g att device i moronicaly tried to download a gsi using the dsu updater, but forgot to unlock bootloader or even enable USB debugging before attempt. So OS system is crashing an saying 'device corrupted' on boot attempt. Recovery mode gets the same result. Was able to use the bugjaegar app to connect ad run the bootloader but every repair attempt is blocked by the fact the USB debugging isn't on. To make matters worse I accidentky hit boot fastbootd command instead of normal and whatever that did wiped out my ability to even connect with bootloader so I'm kind of stuck.

faisaliteb said:
Mod. edit: spammer gone. alecxs
I found many tutorials about fixing bootloops on the Nexus but they all seem to require an unlocked bootloader.
The bootloader on the device is locked. I can see the device in fastboot devices but I can't unlock it.
Any idea how to repair this? Can I somehow flash a factory image onto the device even though OEM unlock is disabled? There is no data on the device that would need to be preserved. I'm ideally looking for a Linux-based solution. more info... ***
Click to expand...
Click to collapse
Yeah man I've been looking at this problem for over a week now and can't find much online at all to help. Except for this EDLmode some devices can boot into, and apparently you can flash a locked system using this emergency download mode. I dunno still researching.