Dear mates,
2 days I am trying to find answer to my problem and finally decided to start new post on exact issue I faced.
device is MI A1 with android one and current version on it was according to picture attached from recovery was tissot_10.0.19. when I took this phone from my mate to fix it was not booting with first MIUI page stacked on the screen.
fastboot output were saying:
--------------------------------------------------
C:\WINDOWS\system32>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.058s]
Finished. Total time: 0.059s
------------------------------------------------
getvar is attached
i tried to flash using miflash ver 2020.3.14 in fastboot mode but it was not successful because of locked bootloader and "locked everything".
i tried to load OTA updates using embedded recovery, but not successful, screenshot attached.
i got the error " E:Error in sideload/package.zip (Status 1)
and all time repeating error : fail to clear BCB message fail to fsync /dev/block/bootdevice/by-name/misc: operation not permitted
any option from recovery meny does not provide any result. wipe data/factory reset were stucking with erasing data notification for hours without result.
at the end i cam to EDL mode by shorting hardware test point. quallcomm driver was ok at computer Device Manager, miflash and QFIL are identifying device on com port 20 but flashing does not finish successfully , it stop at 12 sec in Miflash, and at 1,46% in QFIL. verbose log for QFIL is also attached .
main concern in QFIL log file is "IGNORING UNRECOGNIZED Attribute" stats for attributes from TARGET. my impression is phone is asking to send data in rawmode <?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data> and Qfil is ignoring this attribute. as the result file copy finish with error
23:37:45: INFO: TARGET SAID: 'Finished sector address 131072'
23:37:45: DEBUG: XML FILE (92 bytes): CharsInBuffer=92-92=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" rawmode="false" /></data>
and we have repeating replies from Target as this : <?xml version="1.0" encoding="UTF-8" ?><data><log value="0 bytes received, 1048576 sectors more to go" /></data>
sorry for long explanation, the goal is to share as clear picture of the situation as possible.
i tried the same procedure with QFIL on other computer and had the same result.
now phone is in all time EDL mode. i suppose it is because i checked "erase all before configuration" option in QFIL firehose configurations.
Thanks to everyone in advance for your time and help if you could provide your suggestions how to solve the issue.
I can't solve this problem for more than 4 days and I have android 8.1 and it gives the same problem, you can do the easiest thing, as they say, edl test point, you can try but I don't recommend how you can mess up something if you were able to solve the problem, please tell me how to solve it
Try to flash stock rom via MiFlash Tool. Make sure to see COM port on MiFlash tool (press refresh to detect com port). Then after you see COM port. Flash it with "clean all" option(on the bottom). If you connect to EDL mode properly, process will be finished succesfully. But if you get some "Invalid argument, unknown error" errors, you are not connected to edl mode.
try to enter edl mode with this code in fastboot
Code:
fastboot oem edl
If it give OKAY, then you are ready to flash with Miflash tool.
There is another way to flash img files with fastboot mode. If you dont success, write here.
atc mode is not worked and I don't want to enter the testpoint, how can I tell you and the loader is not open, so this is also not a small problem as you look at it, so if there are other ideas, please send them to me
PLEASEEEEE
Testpoint is a final way. even if you cant enter testpoint, you cant do more
ivomin said:
It's ALIVE!.
Just to update that after debugging the whole windows com stack I struck on a wall and it seems that windows 7 and 10 block something there (I manage to get out of the driver to win kernel on debug but then it fails and didn't had any more nerves to deal with and I'm not a windows guy myself).
So the only solution for low lvl writing is to use linux with point boot to EDL. It seems that for mi A1 even if Qualcomm's boot chain is broken (https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-chains.html) it should fall to EDL in most cases but in our phone (global version at least) it goes to diagnostic mode (not to be confused with Download mode) regardless of drivers in windows - this is hardwired in the chip. So under linux you should fall in to download mode with hardware short of motherboard points to fall in to the correct mode. You should forget about windows as it depends too much on the selected driver (yes you can manually change driver and fu** the whole chain of communication). You need to hardwarely go to Download mode. Don't believe what windows reports.
From there you can use QDL (check documentation on how to install (you'll also need to install gcc (ubuntu - apt get install gcc) https://github.com/96boards/documentation/blob/master/consumer/guides/qdl.md).
Then download a full firmware flash from xiaomi (that's for MiFlash) and use the files in the images folder for the command ( for instance to be more easy copy images folder to qdl folder and:
./qdl --debug --storage emmc --include 'images' 'images/prog_emmc_firehose_8953_ddr.mbn' 'images/rawprogram0.xml' 'images/patch0.xml')
This will fix the first part of the qualcomm bootchain from there you will have access to fastboot and then use all other tutorials concerning fixes from fastboot.
If enough ppl want it I'll write extended tutorial in the other section.
Click to expand...
Click to collapse
Try this. It should bring you to mostly original state and from there you can fastboot unlock and proceed with installing shrp or twrp.
Related
Hello. My phone is accessible only via fastboot and rescue mode.
this appears on screen
func NO: 5 (mcu image)
error no : 1(security verify failed!)
1 .Flashing ROM with this commands is not working, otherwise flashing them is successful
fastboot flash boot BOOT.IMG
fastboot flash recovery RECOVERY.IMG
fastboot flash system SYSTEM.IMG command. *
fastboot flash cust CUST.IMG
2. Recovery option is not accessible
3. EMUI also is not working
4.Phone is unlocked
5.but most of fastboot adb commands are not executable
for instance:
-------- adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error: unknown host service
-------C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem lock
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
6. My IMEI is gone
7. I can't replace mcu.img parition(in order to fix mcu image error), which is obviously the problem, nor boot.img,recovery.img, system.img and cust.img
VERY IMPORTANT INFORMATION !!!
I am in this situation, because my stock ROM had issues with battery, I tried to root device with wrong tool. Than I f****d my stock firmware,not a big deal, easily fixable in various ways. I reinstall and everything was OK, except the fact my IMEI was corrupted. I start a program in one video (please search in youtube " How To Fix Huawei Invailed Imei By Huawei Imei Fixer Tool" ,because I am new user and don't have permission to upload external links) and than inadvertently press number 7 which wasn't my model number.This is the reason why my phone is bricked. I know..... I suck, but please help me. Is my situation fixable or I just have to throw my phone away. Also I have a desire to bring this phone for repair, but only if there is some sense.
Please help me. Thank you. :crying:
coilspring said:
Hello. My phone is accessible only via fastboot and rescue mode.
this appears on screen
func NO: 5 (mcu image)
error no : 1(security verify failed!)
1 .Flashing ROM with this commands is not working, otherwise flashing them is successful
fastboot flash boot BOOT.IMG
fastboot flash recovery RECOVERY.IMG
fastboot flash system SYSTEM.IMG command. *
fastboot flash cust CUST.IMG
2. Recovery option is not accessible
3. EMUI also is not working
4.Phone is unlocked
5.but most of fastboot adb commands are not executable
for instance:
-------- adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error: unknown host service
-------C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem lock
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
6. My IMEI is gone
7. I can't replace mcu.img parition(in order to fix mcu image error), which is obviously the problem, nor boot.img,recovery.img, system.img and cust.img
VERY IMPORTANT INFORMATION !!!
I am in this situation, because my stock ROM had issues with battery, I tried to root device with wrong tool. Than I f****d my stock firmware,not a big deal, easily fixable in various ways. I reinstall and everything was OK, except the fact my IMEI was corrupted. I start a program in one video (please search in youtube " How To Fix Huawei Invailed Imei By Huawei Imei Fixer Tool" ,because I am new user and don't have permission to upload external links) and than inadvertently press number 7 which wasn't my model number.This is the reason why my phone is bricked. I know..... I suck, but please help me. Is my situation fixable or I just have to throw my phone away. Also I have a desire to bring this phone for repair, but only if there is some sense.
Please help me. Thank you. :crying:
Click to expand...
Click to collapse
Try here,it might work to fix your imei
Hi there I have the same problem with my p8lite and your proposed method didnt work for me. Please help
well hello everyone.
motorola G5 plus XT1681
in recent days my phone failed while charging and the legend appeared to me
start up failed
your device didnt start up successfully
use the software repair assistant on computer to repair your device
connect your device to your computer to get the software repair assistant.
ap fastboot flash mode (secure)
failed to pass validation .... ... etc
I already tried to use the motorola software and it did not work, use tools like mfastboot, adb tools, to be able to repair it and nothing works only it sends me errors that it cannot or is blocked
:crying:
on the fastboot screen appeared
AP Fastboot Flash Mode (secure)
BL: C0.92(*) (sha-3ea8df0, 2018- 07-30 18:29:10)
baseband:
product/variant: potter 000000000000000 32gb p3b
serial number: 9cc....063
cpu: msm853
eMMC: 32GB SAMSUNG QX1 3MB RV=08 PV=07 FV=00000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8GB M5=01 M6=05 M7=00 M8=1F
CONSOLE NULL : null
tools mode config: disabled
battery ok
oem_locked
transfer mode: usb
the other menus
start in green letters, switch tools mode in white letters, restart bootloader in red letters, recovery mode in red letters, factory also in red barcodes in white, bp tools in red letters just like Qcon
the oem was not unlocked when the phone worked normally so
They told me that I had to unlock the oem somehow, I tried it with a program called mfastboot but it didn't work
only this appeared:
C:\mfastboot>mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.003s]
finished. total time: 0.006s
I do not know what to do, apart I am a novice in this does not seem very complicated but I already get stuck in the process and I do not know what else to do I hope someone can help me please
Frost817 said:
well hello everyone.
motorola G5 plus XT1681
in recent days my phone failed while charging and the legend appeared to me
start up failed
your device didnt start up successfully
use the software repair assistant on computer to repair your device
connect your device to your computer to get the software repair assistant.
ap fastboot flash mode (secure)
failed to pass validation .... ... etc
I already tried to use the motorola software and it did not work, use tools like mfastboot, adb tools, to be able to repair it and nothing works only it sends me errors that it cannot or is blocked
:crying:
on the fastboot screen appeared
AP Fastboot Flash Mode (secure)
BL: C0.92(*) (sha-3ea8df0, 2018- 07-30 18:29:10)
baseband:
product/variant: potter 000000000000000 32gb p3b
serial number: 9cc....063
cpu: msm853
eMMC: 32GB SAMSUNG QX1 3MB RV=08 PV=07 FV=00000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8GB M5=01 M6=05 M7=00 M8=1F
CONSOLE NULL : null
tools mode config: disabled
battery ok
oem_locked
transfer mode: usb
the other menus
start in green letters, switch tools mode in white letters, restart bootloader in red letters, recovery mode in red letters, factory also in red barcodes in white, bp tools in red letters just like Qcon
the oem was not unlocked when the phone worked normally so
They told me that I had to unlock the oem somehow, I tried it with a program called mfastboot but it didn't work
only this appeared:
C:\mfastboot>mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.003s]
finished. total time: 0.006s
I do not know what to do, apart I am a novice in this does not seem very complicated but I already get stuck in the process and I do not know what else to do I hope someone can help me please
Click to expand...
Click to collapse
Did you turn on OEM unlocking in Dev options before device failed to boot?
If not you cannot unlock the bootloader.
Did you use LMSA'S Flash Rescue option?
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
If that falls your only option is RSD Lite
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Did you turn on OEM unlocking in Dev options before device failed to boot?
If not you cannot unlock the bootloader.
Did you use LMSA'S Flash Rescue option?
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
If that falls your only option is RSD Lite
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I didn't activate it before the device failed, so I guess from your answer I can't unlock it
the rescue tool uses it but it jumps the message of "error when combining files" and if I give the button to read my device then it still gives me an error and tells me that the device is not supported
I will try to use the other tool that you tell me
Frost817 said:
I didn't activate it before the device failed, so I guess from your answer I can't unlock it
the rescue tool uses it but it jumps the message of "error when combining files" and if I give the button to read my device then it still gives me an error and tells me that the device is not supported
I will try to use the other tool that you tell me
Click to expand...
Click to collapse
I suggest you to use this method to flash stock ROM.
https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
and use the latest firmware for your country.
https://mirrors.lolinet.com/firmware/moto/potter/official/
riyan65 said:
I suggest you to use this method to flash stock ROM.
https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
and use the latest firmware for your country.
https://mirrors.lolinet.com/firmware/moto/potter/official/
Click to expand...
Click to collapse
I tried the method but just send me this
[LEFT]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[/LEFT]
Frost817 said:
I tried the method but just send me this
[LEFT]commands:
update reflash device from update.zip
flashall flash boot + recovery + system
flash [ ] write a file to a flash partition
erase erase a flash partition
format format a flash partition
getvar display a bootloader variable
boot [ ] download and boot kernel
flash:raw boot [ ] 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 specify device serial number
or path to device port
-l with "devices", lists device paths
-p specify product name
-c override kernel commandline
-i specify a custom USB vendor id
-b specify a custom kernel base address. default: 0x10000000
-n specify the nand page size. default: 2048
-S [K|M|G] automatically sparse files greater than
size. 0 to disable[/LEFT]
Click to expand...
Click to collapse
That just means you used wrong command, but fastboot.exe rarely works with locked Motorola bootloader anymore
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
That just means you used wrong command, but fastboot.exe rarely works with locked Motorola bootloader anymore
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
mmm I see, that you told try with RSD Lite but the device does not detect me, install the motorola drivers and everything but nothing.
check the windows device manager and it came out as unknown device and restarted the pc again after it appeared
android device
motorola adb interface
I returned to the RSD Lite and still nothing appeared in the box where the device information should appear and in the command prompt if the serial number appears
I use a Windows 10 PC, does that influence or have I skipped a step?
Frost817 said:
mmm I see, that you told try with RSD Lite but the device does not detect me, install the motorola drivers and everything but nothing.
check the windows device manager and it came out as unknown device and restarted the pc again after it appeared
android device
motorola adb interface
I returned to the RSD Lite and still nothing appeared in the box where the device information should appear and in the command prompt if the serial number appears
I use a Windows 10 PC, does that influence or have I skipped a step?
Click to expand...
Click to collapse
RSD Lite doesn't work with Windows 10
Sent from my ali using XDA Labs
sd_shadow said:
RSD Lite doesn't work with Windows 10
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
ok well i changed my pc and i used the RSD Lite again, and this time if the device recognizes me and everything
only that the information of the device appears as N / A in the window and in the list when I run the file of the firmware it sends me
Failed flashing process. 2/22 oem fb_mode_set -> Phone returned fail
while on the phone screen it says
Bootloader logs
cmd: getvar:max-sparce-size
cmd: oem fb_mode_set
I already tried several compatible firmware and all give me the same result
Frost817 said:
ok well i changed my pc and i used the RSD Lite again, and this time if the device recognizes me and everything
only that the information of the device appears as N / A in the window and in the list when I run the file of the firmware it sends me
Failed flashing process. 2/22 oem fb_mode_set -> Phone returned fail
while on the phone screen it says
Bootloader logs
cmd: getvar:max-sparce-size
cmd: oem fb_mode_set
I already tried several compatible firmware and all give me the same result
Click to expand...
Click to collapse
Try
Unzip the .zip
Select flashfile.xml using RSD lite
It doesn't use the fb_mode_set
Sent from my ali using XDA Labs
sd_shadow said:
Try
Unzip the .zip
Select flashfile.xml using RSD lite
It doesn't use the fb_mode_set
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
well don't use the fb_mode_set but it keeps sending me Failure
failed flashing process 1/24 flash partition gpt.bin -> phone returned Fail
bootloader logs:
cmd: getvar- max sparce size
cmd: getvar- max download size
cmd: download 0000b600
cmd: flash: partition
after seeing your post I also believe my phone moto g5 XT1686 failed not able to start, the same issue I tried everything all tools and commands. In a final conclusion Buying Motorola devices is a waste of money.
feeling dishearted...
I have a motorola g4 play (HARPIA) phone, with the latest lineageos version available to ir, it was not used by several months and when turned on it lasted a couple of minutes at the initial screen (the blank one that says the phone is unlocked) and then battery died (my bad)
And now the phone fails at all when starting... it shows an error
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
I have adb & fastboot installed (it is a linux machine), adb do not see the device at all... using fastboot I have tried to flash recovery img file and it shows:
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending ' recovery' (14526 KB) OKAY 0.876 s
Writing 'recovery' OKAY 0.188 s
Finished. Total time 1.423 s
Then tried to go to recovery mode and it fails...:
failed to validate recovery image
ERROR: Failed to pass to pass validaton, backup to fastboot
Boot up failed
Any idea? What to check? what to do? what to try? D-:
A very LONG time ago I have used a windows application, that flashed motorola factory rom files... someone remembers the name? and where to find those factory roms?
At first get Google's up-to-date ADB and fastboot for Linux.
Then get the latest TWRP recovery for harpia.
Then boot yout device to bootloader mode.
Now try the boot-option within fastboot:
--> fastboot boot <twrp-recovery>.img
(Maybe try different USB-cables if this fails)
Now you can install/update TWRP within this booted TWRP instance
--> switch to install image and choose the recovery partition to install it.
Hello,
I have a Nothing Phone 1 that hangs in bootloader/fastboot mode.
The bootloader is unlocked.
Unfortunately, the phone can no longer be booted into recovery mode.
With fastboot the device is still recognized.
So you could still flash files via fastboot.
The phone was not rooted.
The phone previously ran with the original stock firmware 1.1.7 hotfix.
It is an EEA device.
Is there anything that can be done?
Or is it now an expensive paperweight?
Try running "fastboot reboot recovery" in the terminal with your phone connected.
Unfortunately this does not work.
Thanks for the quick reply.
The device then boots back into the bootloader
It looks like they have Nothing OS downloads here. You could just try reflashing the phone through fastboot.
Looks like someone else is having the same problem. Keep an eye on that thread in case a solution comes up there.
so, i have the unpacked payload.bin image files. Here fastboot tells me several errors with odm.img FAILED (remote: '(odm_b) No such partition'), with product.img FAILED (remote: 'Partition not found'), with system.img FAILED (remote: 'Partition not found'), with system_ext.img FAILED (remote: '(system_ext_b) No such partition') and with vendor.img FAILED (remote: 'Partition not found').
After a restart, the error remains.
There is also the fastbootD mode, but this does not work or does not boot.
After this command the device hangs in bootlogo (nothing).
Unfortunately very sad that there is still no solution for this. let's hope that there is soon a solution for this.
Sapphire86 said:
so, i have the unpacked payload.bin image files. Here fastboot tells me several errors with odm.img FAILED (remote: '(odm_b) No such partition'), with product.img FAILED (remote: 'Partition not found'), with system.img FAILED (remote: 'Partition not found'), with system_ext.img FAILED (remote: '(system_ext_b) No such partition') and with vendor.img FAILED (remote: 'Partition not found').
After a restart, the error remains.
There is also the fastbootD mode, but this does not work or does not boot.
After this command the device hangs in bootlogo (nothing).
Unfortunately very sad that there is still no solution for this. let's hope that there is soon a solution for this.
Click to expand...
Click to collapse
Type "fastboot reboot fastboot" in the terminal, with your phone connected, and then run "fastboot flash <yourimagename>.img".
yes, when i enter this command the device restarts and hangs in the bootlogo and in the terminal it says then wait for any device. That means the Nothing Phone does not start the fastbootD mode.
And if he doesn't do this, I think it looks really bad.
Are you using Windows to flash it?
Yes windows 11 with the latest drivers, but I have already considered using linux.
Which linux distribution would be best. Then I will download it and try it out.
I would recommend Ubuntu, if you have a spare computer to install it on (or dual boot). Just make sure you install the tools needed from here (Scroll down to the "Command line tools only" section and download the Linux version)
I only use Linux, so let me know if you have any questions.
Ok thanks. I will have a look and install it on a notebook later.
You have to be very careful. I had the same problem (bootloop in fastboot) and by dint of manipulation, no more fastboot, my smartphone is hard brick (black screen with logo and message key to shutdown)
ziptric1805 said:
You have to be very careful. I had the same problem (bootloop in fastboot) and by dint of manipulation, no more fastboot, my smartphone is hard brick (black screen with logo and message key to shutdown)
Click to expand...
Click to collapse
If your phone has a Qualcomm processor, you still have EDL mode.
It is not bricked. Just flash any cutom rom, I recommend Paranoid Android. Then revert back to stock NOS.
@MakDroid
I just installed Topaz 1 (A13) to save my bricked phone. How can i revert back to stock NOS from A13? There is any option or i have to wait for full rom with A13?
Ostry10 said:
@MakDroid
I just installed Topaz 1 (A13) to save my bricked phone. How can i revert back to stock NOS from A13? There is any option or i have to wait for full rom with A13?
Click to expand...
Click to collapse
Download NOS 1.1.7 full from here.
Extract payload.bin and place all the extracted .img files inside a folder named "images".
Copy the images folder and the attached bat file (extract the zip to get the bat file) to the platform-tools folder.
Run the bat file and it will start flashing. Wait for it to complete and then simply update to latest version using stock updater.
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.