Hi Guys I am Having a problem with my Asus Zenfone Max Pro M2 (X01BDA) , I am not able to flash Twrp or i can't even flash anything via Fastboot.......
When I type the Commands in my PC i get this error :-
While flashing recovery :-
C:\adb>fastboot flash recovery recovery.img
Sending 'recovery' (29664 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
While booting Recovery:-
C:\adb>fastboot boot recovery.img
Sending 'boot.img' (29664 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
i have tried everything but still does'nt work Please help !!!
Check if you are entering the file name correctly with "fastboot flash recovery recovery.img"
Here in recovery.img instead of "recovery" write the filename of the recovery you downloaded.
Is your bootloader unlocked?
same problem here... can't seem find the solution. please help anybody. bootloader has been unlocked, all the name type correctly. but it just FAILED (Write tot device failed (Unknown error)) and the phone suddenly says press any key to shutdown.
richardson2001 said:
Hi Guys I am Having a problem with my Asus Zenfone Max Pro M2 (X01BDA) , I am not able to flash Twrp or i can't even flash anything via Fastboot.......
When I type the Commands in my PC i get this error :-
While flashing recovery :-
C:\adb>fastboot flash recovery recovery.img
Sending 'recovery' (29664 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
While booting Recovery:-
C:\adb>fastboot boot recovery.img
Sending 'boot.img' (29664 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
i have tried everything but still does'nt work Please help !!!
Click to expand...
Click to collapse
RetsuS said:
same problem here... can't seem find the solution. please help anybody. bootloader has been unlocked, all the name type correctly. but it just FAILED (Write tot device failed (Unknown error)) and the phone suddenly says press any key to shutdown.
Click to expand...
Click to collapse
Try this:
1. AMD Bug? - https://forum.xda-developers.com/t/fix-fastboot-issues-on-ryzen-based-pcs.4186321/
2. Switch Device from "Charging" to "File Transfer" Mode
3. Install the latest Device Driver or Universal USB Driver - https://www.androidfilehost.com/?fid=2188818919693784734
4. Placed the latest platform-tools with the Img File directly under the C Drive
5. Try another USB Cable
6. Use another USB Port (USB 3.0 Port to USB 2.0)
7. Try to execute Fastboot Command without connecting your Phone,
and once it says "waiting for device" plug in your USB Cable
8. Windows: Click "Change advanced power setting" on your chosen Plan and expand "USB Settings". Under "USB Settings" Section, expand "USB selective suspend setting" and change it to "Disabled" for On Battery and Plugged In.
9. Try another PC
Code:
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery.img
I hope it helps (∩_∩)
Related
Today I was trying to install a newer rom (MIUI 8.1)(also MIUI 4.11 after the 8.1 failed a couple times) through twrp 3.1.1.0-aries and my mi2s got soft bricked after the update failed with error code 7 something about being unable to write system to /system.
So I tried to install the new rom using MiFlash and got there a different error
Code:
[4:25:07 PM 9063612]:target didn't report max-download-size
[4:25:07 PM 9063612]:sending 'tz' (196 KB)...
[4:25:07 PM 9063612]:error:FAILED (data transfer failure (Unknown error))
[4:25:07 PM 9063612]:"Flash tz error"
[4:25:07 PM 9063612]:error:FAILED (data transfer failure (Unknown error))
Then I tried to flash it using Mi PC Suite which got stuck at 52% for 2 hours at "sending system.img". I saw it wasn't going anywhere so I disconnected the device and terminated the task.
At that point the phone didn't go into the recovery mode anymore. I think Mi PC Suite might have done something to the partition table.
Right now the phone is stuck in fastboot loop and can't go into recovery mode unless I run the command
Code:
fastboot boot twrp.img
which can sometimes fail as well with error:
Code:
FAILED (status read failed (Too many links))
At the first time I managed to get back into twrp using the above command I felt some relief and I tried doing a factory reset from the twrp menu. It didn't help.
Flashing twrp using the command
Code:
fastboot flash recovery twrp.img
says everything is okay and is finishing without errors but I still can't boot into it. It just goes straight to fastboot.
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (10346 KB)...
OKAY [ 0.432s]
writing 'recovery'...
OKAY [ 1.793s]
finished. total time: 2.225s
trying to flash new rom using MiFlash gives an error about the partition table
Code:
FAILED (remote: partition table doesn't exist)
Please help me unbrick my device I'm open for suggestions!
Thank you.
I fixed this by downloading "aries_images_4.11.21_4.1_cn" and editing the "flash_all.bat" script to include
Code:
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @echo "Flash partition error" && exit /B 1
in the third row right after the 2 "soc-id" checks.
I am still not sure how to upgrade from here to one of the newer miui roms.
XDA1515 said:
I fixed this by downloading "aries_images_4.11.21_4.1_cn" and editing the "flash_all.bat" script to include
Code:
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @echo "Flash partition error" && exit /B 1
in the third row right after the 2 "soc-id" checks.
I am still not sure how to upgrade from here to one of the newer miui roms.
Click to expand...
Click to collapse
Solved. I managed to flash aries_global_images_V8.1.3.0.LXAMIDI_20161122.0000.00_5.0_global using MiFlash.
At first I thought it didn't work because it flashed the whole rom way too quickly in like 5-10 seconds and booted back to fastboot but then I just left the device there to rest and when I came back after a few minutes I saw it booted to a black screen with a white MI at the center of it and then android and 3 dots appeared at the bottom so I just waited for a few more minutes and it installed everything.
I hope this might help someone else with similar issue.
Hello
i have followed all the guides in order to install the latest version of TWRP in mi X Compact in order to Magisk, but im having this issue on the fastboot comand:
Sending 'recovery' (21552 KB) OKAY [ 0.724s]
Writing 'recovery' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
i have serched for solutions but nothing seems to work, its the first time i try to install TWRP on this phone so its never been rooted (Bootloader is not unlocked) and everyting has alredy been updated to the latest version, any help?
Thanks in advance!
i just unlocked the bootloader, and still gives me the "FAILED (remote: Command not allowed)" error when flashin TWRP trough fastboot HELP PLEASE
Black Swift said:
i just unlocked the bootloader, and still gives me the "FAILED (remote: Command not allowed)" error when flashin TWRP trough fastboot HELP PLEASE
Click to expand...
Click to collapse
Try fastboot boot twrp.img
just tried it, i got a message on my phone screen:
"your device has failed verification and will not work properly"
then phone restarts
in the windows power shell i get this message:
FAILED (Status read failed (Too many links))
I just seem to be unable to install TWRP on this phone :C
Help please!!!
i just tried a different cable, im still getting the "comand not allowed" message, can anyone help me please??
Hi,
Today My Asus Zenfone AR stopped working with no apparent reasons or actions performed by me.
When I try to turn it on, it simply remains stuck on the ASUS log screen.
I tried to trigger the recovery mode (POWER+VOLUME DOWN button ) with no success (nothing happens)
I tried POWER+VOLUME UP and I got the fastboot screen. The following infos are displayed:
PRODUCT_NAME - Siva
STORAGE VARIANT - UFS
BOOTLOADER VERSION - 1.21
VERSION - WWZS571KL-14.1600.1712.41
SECURE BOOT - enabled
DEVICE STATE - locked
From the menu I can select 1)start, 2)power off, 3)recovery mode, 4)restart bootloader.
Nothing seems to work, in particular if i select recovery mode, the phone reboots but it remains stuck in the logo again.
Then I tried to follow the steps described by you in: https://forum.xda-developers.com/zenfone-ar/development/recovery-twrp-touch-recovery-t3767745.
adb.exe version 29.0.6-6198805, running on windows10, seems not recognize the device while the phone is in fast boot mode (adb devices shows no output)
Instead, the device is recognized by fastboot.exe (same version). I tried the following four commands with no success:
1) fastboot flashing unlock
FAILED (remote: 'unknown command')
2) fastboot oem unlock
FAILED (remote: 'unknown command')
3) fastboot oem asus-go
(bootloader) Fail to unlock device due to invalide signature!
OKAY [ 0.036s] Finished. Total time: 0.042s
4) fastboot flash recovery twrp-3.2.1-0_CPTB-20180323-03-A002.img
Sending 'recovery' (18672 KB) OKAY [ 0.466s]
Writing 'recovery' FAILED (Status read failed (Too many links))
fastboot: error: Command failed
The phone then turns off.
I suspect the last command failed because of the device is locked but I cannot find a procedure to unlock it from fastboot. (anyway, I have zero experience on android firmware etc).
Can you suggest me on how to proceed?
I am using the OnePlus 7 port for zenfone max pro m1. I was trying to change my recovery from twrp to orange fox recovery but I was unable to do so. It gave me the following error
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\recovery.img
target didn't report max-download-size
sending 'recovery' (28872 KB)...
FAILED (command write failed (No error))
finished. total time: 0.034s
I tried to flash the orange fox recovery image through twrp and it got flashed, since then my phone doesn't boot into recovery. it gets stuck at the asus logo. I tried to reset my phone to factory settings using the stock firmware but when i run the "flashall_AFT.bat" file, my phone shows the message "press any key to shutdown" and there is no progress in the command prompt window. Now I cant boot into recovery mood and cant flash anything through fastboot. Anyone has any idea on how to fix this issue?
If i get these message, i am sure, the usb-port is incompatible for the fastboot (maybe the usb3 and fastboot incompatibility, but i'm not sure). Try to use some old usb-hub between phone, and PC.
Uniformatom said:
I am using the OnePlus 7 port for zenfone max pro m1. I was trying to change my recovery from twrp to orange fox recovery but I was unable to do so. It gave me the following error
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\recovery.img
target didn't report max-download-size
sending 'recovery' (28872 KB)...
FAILED (command write failed (No error))
finished. total time: 0.034s
I tried to flash the orange fox recovery image through twrp and it got flashed, since then my phone doesn't boot into recovery. it gets stuck at the asus logo. I tried to reset my phone to factory settings using the stock firmware but when i run the "flashall_AFT.bat" file, my phone shows the message "press any key to shutdown" and there is no progress in the command prompt window. Now I cant boot into recovery mood and cant flash anything through fastboot. Anyone has any idea on how to fix this issue?
Click to expand...
Click to collapse
Use a Good quality usb cable or connect your mobile to usb 2.0 of your pc
It happened to me too , using a normal cable in usb 2 port . and and no problem in usb 3 port.
why i cant fastboot
Same problem I got.
Running the command (on Linux)
Bash:
~/platform-tools/fastboot flash recovery recovery.img
I get:
Code:
Sending 'recovery' (21101 KB)
...and that's it. Fastboot hangs indefinitely, seemingly not sending anything, and can only be killed by unplugging the USB. The phone says "FASTBOOT MODE" in green. I've tried all 3 USB ports on my laptop, the paths and filenames are correct, i've tried a lot and using both twrp and LineageOS recovery images, but I never get beyond this, except for getting an error sometimes, "FAILED (Write to device failed (Protocol error))", "FAILED (remote: 'unknown command')", or "FAILED (Write to device failed in SendBuffer() (Protocol error))", which turns into this after rebooting fastboot mode or trying again. What am I missing? I've unlocked the bootloader with the app, I'm trying to install a recovery to install LineageOS.
Edit: Doesn't seem like there's a solution, but I tried another computer and it worked. Annoying how buggy it is, but there.