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
Folks,
I have a ZF2L aka ZE551KL which is currently in a bootloop. Why that happened I have no idea as I have not dinked with the stock rom or for that matter even unlocked the bootloader.
A little bit of history, over the weekend, I had plugged in my phone to charge it and then when it completed charging I unplugged it and then tried to reboot it. That was the last time I had it working. After the reboot the phone has been in a bootloop ever since.
In order to try to recover from the above, I started reading a bit on what to do and I came across the postings that mentioned the bootloader has to be dropped to the Lollipop level so that it can be unlocked and then the recovery can be upgraded to Marshmallow. While trying to get all of that done, I have ended up here.
I "think" I have unlocked the bootloader using the command
echo -ne "\x01" | dd obs=1 count=1 seek=16 of=/dev/block/bootdevice/by-name/devinfo
I ran the above command directly on the phone via the terminal in TWRP. I booted into TWRP using the following fastboot command
fastboot boot twrp-3.2.3-0-Z00T.img
Running the fastboot command, fastboot oem device-info gives me the following output
C:\Users\home\android\platform-tools\images>fastboot oem device-info
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
Finished. Total time: 0.016s
However when I try to flash a new recovery TWRP-3.2.3-0-Z00T I get the following error
C:\Users\home\android\platform-tools\images>fastboot flash recovery twrp-3.2.3-0-Z00T.img
Sending 'recovery' (29856 KB) OKAY [ 1.342s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
Finished. Total time: 1.388s
I'm a little lost on what's going on. The device-info tells me the bootloader is unlocked, however it appears that something else is still locked which is not allowing the recovery to get flashed.
The stock recovery I was on before this all started was asus/WW_Z00T/ASUS_Z00T/6.0.1/MMB29P/WW_user_21.40.1220.2181_20170805. The recovery I currently have is LRX22G.WW_user_1.16.40.763_20151201
Any pointers on what I could do to get this resolved would be helpful?
hi if ur bootloader is unlocked, u an do a fresh flash of all d partitions as sometimes things get messed up on its own.
download firmware from https://drive.google.com/file/d/0B43Ue6xY9MmdN0UzWVRFcno4N0U/view and extract, then run flashall.cmd (in fastboot mode i.e. pwr and vol up)
u should finish without any hiccups. u will lose twrp though
tried on mine it woks. but google frp may be active so keep ur email n pass handy. m not responsible for any damages though ...
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 (∩_∩)
I'm trying to root my Huawei P8 Lite 2017 PRA-LX1 (running on EMUI 5.0.3 Android 7.0). But I'm getting stuck :
My BootLoader is unlock, but my FRP is locked when I access the fastboot mode.
The option Allow OEM unlock is turned off and greyed out in the dev settings.
It prevents me from doing any command with fastboot, except "fastboot devices" and "fastboot oem get-bootinfo". All other commands return me :
Code:
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
I'm worried cause it looks like I no longer have a recovery img : when I boot with Vol UP + Power, I got a screen with the Android guy saying :
Code:
ERROR MODE
Attention !
Please Update system again
Error
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Each time I boot, I have a black screen with white and yellow writtings saying
"your devices has been unlocked and cannot be trusted"
From there I can boot normaly to the standard OS (EMUI 5.0.3 ; Android 7.0).
I can also enter the eRecovery mode to download latest version and recovery. But it fails and say "Getting package info failed".
When I try the factory reset from the settings, I get the same error as the one I got when trying to access the recovery more :
Code:
ERROR MODE
Attention !
Please Update system again
Error
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
To get to this situation, I tried to follow this guide :
[GUIDE] Unlock bootloader, root the device and install any custom ROM! (ALE-L23/21)
Hi all! So, you have a P8 lite in your pocket and you hate EMUI? Well, that was my case too, it's uncustomizable, ugly, and removes plenty of features from android stock. I do not like it one bit, and I like even less the fact that this phone is...
forum.xda-developers.com
I was not able to flash any OS with the dload/ procedure.
So I followed this guide :
[UPDATED GUIDE] [BOOTLOADER UNLOCK] Huawei p8 lite 2017 (pra-lx1)
This guide is the only one made and tested personally by me, I am not responsible for malfunctions or any damage to the device, carefully read every single step and everything will be successful [ATTENTION]: Before proceeding, save all your...
forum.xda-developers.com
and was able to correctly unlock my bootloader.
Then, I got back to the first guide to Install TWRP. The command fastboot flash recovery was working well :
Code:
$ fastboot flash recovery twrp-3.6.2_9-0-prague.img
Sending 'recovery' (14998 KB) OKAY [ 0.430s]
Writing 'recovery' OKAY [ 0.370s]
Finished. Total time: 0.828s
But I never managed to enter the TWRP recovery.
The Vol UP + Power reboot was getting me the eRecovery mode (to install the standard OS).
I tried to enter TWRP with fastboot :
Code:
$ fastboot boot twrp-3.6.2_9-0-prague.img
Sending 'boot.img' (14998 KB) OKAY [ 0.420s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Trying to solve this situation have made the things worse and worse.
I would like to follow this tutorial
[Solution]BL unlocked&FRP Locked-Fastboot FAILED (remote: Command not allowed)
Note: THIS IS NOT A SOLUTION TO BYPASS FRP! I am not responsible if you are dumb dumb and break your phone This Solution is written in under 10 minutes AND WORKS ONLY AND ONLY FOR STOCK people with no experience stay away This is not a...
forum.xda-developers.com
but since I cannot do a factory reset (first step tutorial) and I don't have a recovery img working, I'm a bit timorous.
Do you think I can upgrade my OS (from my OS settings menu) without a recovery img ? Will that solve the issue with my recovery img ?
Any thoughts on the situation would be much appreciated.
Thanks for reading me !
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.