Followed the other threads without success, in my stupidity yesterday i wiped the boot
have install android sdk and google driver, htc syc with drivers, tried an RUU without success, copied clockwork recovery and ran the following:
C:\android-sdk-windows\tools>fastboot boot recovery-clockwork-2.5.0.7-hero.img
but receive the following:
downloading 'boot.img'...
FAILED (remote: not allow)
finished. total time: 0.001s
Help please just getting fastboot usb on the htc splash screen, unable to physically get into the phone to make any dev setting changes.
Extracted AndroidSDK downloaded google usb driver, manually changed driver from HTC Bootloader to Google USB driver now showing as 'Android 1.0'
Tried 'via fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors'
http://forum.xda-developers.com/showthread.php?t=561124
C:\AndroidSDK\platform-tools>adb shell reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Also tried
C:\AndroidSDK\tools>fastboot flash recovery cm-hero-recovery.img
sending 'recovery' (3972 KB)...
FAILED (remote: not allow)
finished. total time: 0.002s
Sorted
wasnt holding down the home key long enough after reboot to get into recovery
back on android 2.3.5
yeah it's pretty helpful to have a s-off bootloader. just in case something gets really fubar
Related
Hi all,
My Wildfire is not recognized by the unrevoked 3, anymore ...
Unrevoked was displaying a message like device "" not yet recognized.
The recovery partition is not accessible and I've tried to reinstall a nandroid backup with fastboot but :
G:\android-sdk_r07-windows\android-sdk-windows\tools>fastboot boot recovery
creating boot image...
creating boot image - 753664 bytes
downloading 'boot.img'... OKAY [ 0.328s]
booting... FAILED (remote: not allowed)
finished. total time: 0.328s
Currently, the device is starting and asking to kill multiple task to finaly restart...
The effect is that I can't access to the parameter to set usb to dev
For info :
G:\android-sdk_r07-windows\android-sdk-windows\tools>fastboot devices
HT09LPY077XX fastboot
Could someone help me
Thanks a lot
NoXoZ said:
Hi all,
My Wildfire is not recognized by the unrevoked 3, anymore ...
Unrevoked was displaying a message like device "" not yet recognized.
The recovery partition is not accessible and I've tried to reinstall a nandroid backup with fastboot but :
G:\android-sdk_r07-windows\android-sdk-windows\tools>fastboot boot recovery
creating boot image...
creating boot image - 753664 bytes
downloading 'boot.img'... OKAY [ 0.328s]
booting... FAILED (remote: not allowed)
finished. total time: 0.328s
Currently, the device is starting and asking to kill multiple task to finaly restart...
The effect is that I can't access to the parameter to set usb to dev
For info :
G:\android-sdk_r07-windows\android-sdk-windows\tools>fastboot devices
HT09LPY077XX fastboot
Could someone help me
Thanks a lot
Click to expand...
Click to collapse
try restoring from rru (1.25, find it on shipped roms (or search the fourm for restoring the rru)
Device is unlocked (A2017G)
Tried flashing twrp/root using axon7toolkit(version 1.2.0)
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Can anybody help with this?
still_living said:
Device is unlocked (A2017G)
Tried flashing twrp/root using axon7toolkit(version 1.2.0)
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Can anybody help with this?
Click to expand...
Click to collapse
edit: whatever, i'll let bkores help you with this
still_living said:
Device is unlocked (A2017G)
Tried flashing twrp/root using axon7toolkit(version 1.2.0)
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Can anybody help with this?
Click to expand...
Click to collapse
Do this in command prompt and tell me the output:
Code:
cd C:\Axon7Development\Axon7Toolkit
fastboot flash recovery twrp\twrp-3.1.1-0-ailsa_ii.img
Also failed
bkores said:
Do this in command prompt and tell me the output:
Code:
cd C:\Axon7Development\Axon7Toolkit
fastboot flash recovery twrp\twrp-3.1.1-0-ailsa_ii.img
Click to expand...
Click to collapse
This is what I got.
C:\Axon7Development\Axon7Toolkit>fastboot flash recovery twrp\twrp-3.1.1-0-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (14452 KB)...
OKAY [ 0.362s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.383s
I have a big problem with my old phone. Well, I have a HTC Desire 310 which was not used for a long time, after launch stopped on the logo. Then I decided to install stock rom. I downloaded a rom from a Russian site, then installed the MediaTek USB VCOM drivers and the FlashTool SP program.
The problem is that I broke something that the phone has bootloop and at the bottom of the message "TOOL DL Image Fail!". When I try to flash the rom with the battery after 9 seconds to restart and without battery after 2 seconds and disappears from the device manager.
I do not remember if this phone had administrator privileges
I downloaded various versions of FlashTool and drivers from different sources and nothing
Does anyone have any ideas what else can be done?
I used these guides:
https://forum.xda-developers.com/android/help/tuto-how-to-unbrick-htc-desire-310-dual-t3057203
https://forum.xda-developers.com/general/rooting-roms/guide-mediatek-spflashtool-failure-t2936933
https://forum.xda-developers.com/showthread.php?t=1982587
PS. Please excuse my English, if someone does not understand something I will try to explain more clearly.
I solved part of the problem. After many attempts to install rom. The next problem is unlocking the bootloader.
There are further problems. To enter fastboot I was write adb reboot-bootloader into the console (volume - and power not working).
Then a black screen appears and a small inscription FASTBOOT mode... .
When I enter the command fastboot device my device is visible but after entering command fastboot oem get_identifier_tokenit three dots appear and nothing happens
Another problem is the incorrect CID. I do not know if you have to download the bootloader first or change the CID
Currently, in fastboot mode, no commands work except fastboot devices.
I get errors when I type fastboot getvar:
Code:
fastboot: getvar version
fastboot out: getvar:version FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar version-bootloader
fastboot out: getvar:version-bootloader FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar version-main
fastboot out: getvar:version-main FAILED (remote: not support on security)
finished. total time: 0.003s
help
Exacty same problem. Someone please help what can i do?
Thank you very much
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.