Hi all, really annoying problem where my phone is stuck in a fastboot loop. The phone loads into fastboot and if it is plugged into the PC via USB it keeps rebooting into fastboot. I can use this command 'fastboot oem fb_mode_clear' when it's about to load and it sometimes causes it to stop rebooting. As soon as I input another command like fastboot devices, it begins the loop again. It also only shows ?????? as the device name.
Is there anything I can do if I do manage to get it to stop rebooting while it's connected to the PC? Thanks.
An example of the rebooting -
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
< waiting for any device >
...
FAILED (command write failed (No error))
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
< waiting for any device >
...
FAILED (remote: unknown command)
finished. total time: 0.014s
Here's what happens when I try and flash the factory image:
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\flash-all.bat
target didn't report max-download-size
sending 'bootloader' (55680 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.005s
< waiting for any device >
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
< waiting for any device >
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.003s
W/ziparchive(133904): Unable to open 'image-taimen-opd1.170816.010.zip': No such file or directory
error: failed to open zip file 'image-taimen-opd1.170816.010.zip': I/O error
Press any key to exit...
This is the best I've done I think...
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target didn't report max-download-size
sending 'bootloader' (55680 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.009s
< waiting for any device >
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (command write failed (No error))
finished. total time: 0.005s
< waiting for any device >
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.009s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.199s
target didn't report max-download-size
archive does not contain 'boot.sig'
extracting dtbo.img (8 MB) to disk... took 0.023s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1866 MB) to disk... took 9.931s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (341 MB) to disk... took 2.077s
archive does not contain 'vendor.sig'
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (No error))
finished. total time: 0.012s
Press any key to exit...
Hi, in case you stumble on this self-rambling thread looking for an answer, it turns out changing the port fixed it. In my case I plugged it into a usb-c hub that had usb-a ports and that allowed it to work properly. God knows why, but worth a shot if anybody is having issues with their PC's usb ports.
Related
Exuse me for my bad English, because A'm from Russia ...I want to return to the offiсial rom of HTC ONE X. But i have any problems... When I do
cd c:\Android \Android>fastboot flash recovery recovery.img
sending 'recovery' (5742 KB)...
FAILED (remote: (00120000))
finished. total time: 0.002s \Android>fastboot oem lock ...
FAILED (unknown status code)
finished. total time: 0.000s \Android>fastboot oem lock ...
OKAY [ 0.000s]
finished. total time: 0.000s \Android>
Then i run official rom and it has problem...mistake [140] Wrong version of loader. Is it anybody help me what to do with it?
http://forum.xda-developers.com/showthread.php?t=1660807
I foolishly let my battery on my HOX completely empty and now I'm having the common charging problem. I can get into bootloader if I have it connected to a mains charger, so I thought I'd give the batch script a go that is all over the net:
Code:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
How I can't seem to cycle the loop - the output is as follows:
Code:
C:\htc>charge.bat
< waiting for device >
battery-voltage: 884mV
finished. total time: 0.207s
rebooting into bootloader...
OKAY [ 0.256s]
finished. total time: 0.257s
getvar:battery-voltage FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
getvar:battery-voltage FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.001s
getvar:battery-voltage FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.001s
getvar:battery-voltage FAILED (command write failed (No such file or directory))
Note I am using stock, not a custom ROM.
I suspect I have so little battery (884mV!!!) that it is completely buggered. But I'd welcome any suggestions people might have. I tried all the normal power/vol buttons combinations, I've tried recovery from bootloader, and I've tried just leaving it on mains charge overnight. No joy.
Hey
when i want to flash the factory image from google with the "flash-all.bat" i got this Error.
failed to allocate 2008772888 bytes
error: update package missing system.img
i tried to flash manualy dosent work too.
J:\fastboot\bullhead-mmb29p>fastboot flash system system.img
load_file: could not allocate 2008772888 bytes
error: cannot load 'system.img'
this comes when i run the "flash-all.bat"
sending 'bootloader' (4382 KB)...
OKAY [ 0.213s]
writing 'bootloader'...
OKAY [ 0.137s]
finished. total time: 0.352s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.012s
sending 'radio' (56614 KB)...
OKAY [ 1.807s]
writing 'radio'...
OKAY [ 0.506s]
finished. total time: 2.315s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 2008772888 bytes
error: update package missing system.img
Press any key to exit...
please help me:crying:
use newest fastboot. Had the same failure on Nexus 9 - flounder.
Donald Nice said:
use newest fastboot. Had the same failure on Nexus 9 - flounder.
Click to expand...
Click to collapse
many many thanks :good:
you safed the life from my 5x ♥
Donald Nice said:
use newest fastboot. Had the same failure on Nexus 9 - flounder.
Click to expand...
Click to collapse
Hello, sorry for my English, i've download the Minimal fastboot and adb file and i've installated it. but it styll doesn't work, when i try to type te command: fastboot flash system system.img, the result is error: cannot load system.img. what can i try to do?
Download and install SDK Manager. Later, install SDK tools, SDK Platform Tools, Android support library and Google USB driver. Then try again.
I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
matthew.bridell said:
I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
Click to expand...
Click to collapse
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
CyberpodS2 said:
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
Click to expand...
Click to collapse
flash the zip? Would I just use fastboot flash image-taimen-opm1.171019.018.zip ?
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
CyberpodS2 said:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Click to expand...
Click to collapse
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
I was able to install Lineage-15.1-20180219 and boot into it. Tried to restore from that point and it now when I run flash-all it now says
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.006s
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
error: cannot load system.img from flash
Press any key to exit...
matthew.bridell said:
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
Click to expand...
Click to collapse
You need to update your platform-tools.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
just tried the zip and no luck
C:\Users\matth\Downloads>cd "platform-tools-latest-windows (2)"
C:\Users\matth\Downloads\platform-tools-latest-windows (2)>cd platform-tools
C:\Users\matth\Downloads\platform-tools-latest-windows (2)\platform-tools>flash-all
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.005s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.221s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
I do now have default Recover but don't know why it won't work.
I feel dumb. I got it to work with using a usb-a to usb-c cord. was trying to use the usb-c to usb-c cord thanks for all the help.
no upgread mode vol up+ + vol- + power / no fastboot to ececovery
fastboot info
bootloader)
OKAY [ 0.005s]
finished. total time: 0.006s
Reading Mobile Version Info
...
(bootloader) :Error: /preas/xxx not found in /product/hw_oem/EVR-AL00/par
FAILED (unknown status code)
finished. total time: 0.006s
Reading Mobile Bootloader Lock Info
Could Not Find C:\Program Files (x86)\Bonjour\mdnsNSP.dll.dat
The directory name is invalid.
...
FAILED (command write failed (Unknown error))
finished. total time: 5.001s
Reading Mobile Battery Info
...
FAILED (command write failed (Unknown error))
finished. total time: 0.000s
Reading Mobile vendor and country Info
< waiting for device >
vendorcountry: all/cn
finished. total time: 0.021s
all is done
Top