My phone is no flash,no root, no USB debugging. Can't boot after OTA update today, stuck at Fastboot Mode, can't start. the error message is "failed to load/verify boot images"
I download Redfin from Factory Images for Nexus and Pixel Devices, run flash-all.bat, error message:
Code:
Sending 'bootloader_a' (8762 KB) OKAY [ 0.328s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.048s]
Finished. Total time: 0.051s
Sending 'radio_a' (149796 KB) OKAY [ 3.886s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
--------------------------------------------
Bootloader Version...: r3-0.4-8351081
Baseband Version.....: g7250-00202-220422-B-8489468
Serial Number........: 09
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.169s]
Checking 'version-bootloader' OKAY [ 0.178s]
Checking 'version-baseband' OKAY [ 0.139s]
Setting current slot to 'a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Press any key to exit...
I run:
[ICODE]# fastboot flashing unlock
FAILED (remote: 'Error getting device locked state Not Ready')
fastboot: error: Command failed[/ICODE]
fastboot boot boot.img
Sending 'boot.img' (98304 KB) OKAY [ 2.400s]
Booting FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
fastboot devices
09aaaaaaaaaa fastboot
please help me
Have you tried simply re-flashing?
Sewdohe said:
Have you tried simply re-flashing?
Click to expand...
Click to collapse
yes, but it can't open, He still remains in "Fastboot Mode" and cannot be started
Barbet is Pixel 5a.
Redfin is Pixel 5
andybones said:
Barbet is Pixel 5a.
Redfin is Pixel 5
Click to expand...
Click to collapse
sorry, I look my download folder, it is "redfin-sq3a.220705.003.a1-factory-b193f96f"
Evolv X said:
sorry, I look my download folder, it is "redfin-sq3a.220705.003.a1-factory-b193f96f"
Click to expand...
Click to collapse
Did using the correct file fix your problem?
NO, and I use Google Online, Bug can't
V0latyle said:
Did using the correct file fix your problem?
Click to expand...
Click to collapse
Evolv X said:
NO, and I use Google Online, Bug can't
Click to expand...
Click to collapse
Could you be a bit more detailed? I don't understand.
Same, I don't understand. It appears you're trying to flash for the wrong phone...
If your bootloader is locked, you cannot flash anything in fastboot/bootloader.
Try sideloading the OTA again.
Getting this issue...are you able to fix it?
Related
Hi
I had TWRP installed and installed Cm12.1-20150427 unoffical-yuga and Cyanogenmod wrote its own recovery.
If I try to install any zips such as
extract_elf_ramdisk-hack.zip
twrp-2.8-20150424-yuga.zip
I get the error:
E:footer is wrong
E:signature verification failed
If I try ADB
fastboot flash recovery recovery.img
I get
sending 'recovery' (10388 KB)...
OKAY [ 0.446s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.458s
I'm stuck any ideas?
Thanks
What i did and it worked really fine is to use the Rashr utility (free from Google Store) and just fhlash the twrp image.
Try it!
cramhead said:
Hi
I had TWRP installed and installed Cm12.1-20150427 unoffical-yuga and Cyanogenmod wrote its own recovery.
If I try to install any zips such as
extract_elf_ramdisk-hack.zip
twrp-2.8-20150424-yuga.zip
I get the error:
E:footer is wrong
E:signature verification failed
If I try ADB
fastboot flash recovery recovery.img
I get
sending 'recovery' (10388 KB)...
OKAY [ 0.446s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.458s
I'm stuck any ideas?
Thanks
Click to expand...
Click to collapse
i have another huawei device, but not honor play.
Now the display can't show me anything even if I press the power button.
Then i connected my phone to my computer and i found that my phone had automatically booted bootloader without showing me anything on its display
i entered fastboot flash recovery recovery.img
it said failed remote command not allowes
i entered fastboot oem relock (password)
it said OKAY
i entered fastboot oem unlock (password)
it said OKAY
i entered fastboot flah boot boot.img
it said failed remote partition length get erro
i used hisuit but it failed when flashing recovery
So i can hardly do anything
how to deal with the problem?
pls help me
thank u
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Can you enter erecovery??
Nwereonye said:
Can you enter erecovery??
Click to expand...
Click to collapse
No. the phone cant show me anything. if i try to turn it off, it will restart.(according to my computer)
rajit said:
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Click to expand...
Click to collapse
I'm busy these days. I'll post the log some days later
rajit said:
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Click to expand...
Click to collapse
Today I download a package for my device from Firmware finder for Huawei. Then I used Huawei Update Extractor to extract some of the files and tried to flash them to my phone. But failed.
Here's the log
PS C:\WINDOWS\system32> fastboot devices
3CG4C16817019572 fastboot
PS C:\WINDOWS\system32> fastboot flash boot C:\Users\yyche\Desktop\update\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (15494 KB)...
OKAY [ 0.400s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.430s
PS C:\WINDOWS\system32> fastboot flash crc C:\Users\yyche\Desktop\update\CRC.img
target reported max download size of 471859200 bytes
sending 'crc' (161 KB)...
OKAY [ 0.006s]
writing 'crc'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
PS C:\WINDOWS\system32> fastboot flash fastboot C:\Users\yyche\Desktop\update
error: cannot load 'C:\Users\yyche\Desktop\update'
PS C:\WINDOWS\system32> fastboot flash fastboot C:\Users\yyche\Desktop\update\FASTBOOT.img
target reported max download size of 471859200 bytes
sending 'fastboot' (3128 KB)...
OKAY [ 0.081s]
writing 'fastboot'...
FAILED (remote: Command not allowed)
finished. total time: 0.092s
PS C:\WINDOWS\system32> fastboot flash recovery C:\Users\yyche\Desktop\update\RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (35540 KB)...
OKAY [ 0.914s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.946s
PS C:\WINDOWS\system32> fastboot oem unlock 1**************4
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.004s
Do not flash the latest version, it seems u r tying to flash Android Pie. Try to flash Oreo (8.0) version of rom or the one that comes factory installed.
anyone seen this before?
Sending 'bootloader_a' (8761 KB) OKAY [ 0.321s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.045s]
Finished. Total time: 0.053s
< waiting for any device >
Sending 'radio_a' (82676 KB) OKAY [ 2.098s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.155s
< waiting for any device >
--------------------------------------------
Bootloader Version...: c2f2-0.2-5940465
Baseband Version.....: unknown
Serial Number........: 98011FFC4004AN
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED
Device product is 'unknown'.
Update requires 'flame' or 'coral'.
fastboot: error: requirements not met!
Press any key to exit...
thatotherguy.. said:
anyone seen this before?
Sending 'bootloader_a' (8761 KB) OKAY [ 0.321s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.045s]
Finished. Total time: 0.053s
< waiting for any device >
Sending 'radio_a' (82676 KB) OKAY [ 2.098s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.155s
< waiting for any device >
--------------------------------------------
Bootloader Version...: c2f2-0.2-5940465
Baseband Version.....: unknown
Serial Number........: 98011FFC4004AN
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED
Device product is 'unknown'.
Update requires 'flame' or 'coral'.
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse
Is this the first time this has happened?
Fastboot up to date?
Are you using power shell?
Tried USB A to USB C cables and different USB ports?
Did you extract the factory image and place all the contents in the platform-tools folder?
Device drivers are up to date?
Did you see your phone ID # when you typed in "fastboot devices"?
Badger50 said:
:
Click to expand...
Click to collapse
Is this the first time this has happened? someone was trying to flash stock before
Fastboot up to date? Yes it is, I just flashed another phone just fine before this one
Are you using power shell? no I am using cmd
Tried USB A to USB C cables and different USB ports? yes I have
Did you extract the factory image and place all the contents in the platform-tools folder? yes
Device drivers are up to date? yes they are
Did you see your phone ID # when you typed in "fastboot devices"? yes it show up, but it no picture show on screen even though the pc see it
thatotherguy.. said:
Is this the first time this has happened? someone was trying to flash stock before
Fastboot up to date? Yes it is, I just flashed another phone just fine before this one
Are you using power shell? no I am using cmd
Tried USB A to USB C cables and different USB ports? yes I have
Did you extract the factory image and place all the contents in the platform-tools folder? yes
Device drivers are up to date? yes they are
Did you see your phone ID # when you typed in "fastboot devices"? yes it show up, but it no picture show on screen even though the pc see it
Click to expand...
Click to collapse
Are you sure the bootloader is unlocked?
Badger50 said:
Are you sure the bootloader is unlocked?
Click to expand...
Click to collapse
I'm not 100% sure of that, the other phone they have it was unlocked. but this one doesn't show baseband as unknown
thatotherguy.. said:
anyone seen this before?
Sending 'bootloader_a' (8761 KB) OKAY [ 0.321s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.045s]
Finished. Total time: 0.053s
< waiting for any device >
Sending 'radio_a' (82676 KB) OKAY [ 2.098s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state No Response')
Click to expand...
Click to collapse
thatotherguy.. said:
I'm not 100% sure of that, the other phone they have it was unlocked. but this one doesn't show baseband as unknown
Click to expand...
Click to collapse
Judging from all the "getting device locked state" warnings your getting, I'd say it's still locked.
Badger50 said:
Judging from all the "getting device locked state" warnings your getting, I'd say it's still locked.
Click to expand...
Click to collapse
guessing pretty it done for?
thatotherguy.. said:
guessing pretty it done for?
Click to expand...
Click to collapse
Huh?? If you want to unlock it, make sure OEM unlocking and USB debugging is turned on in developer options. Then go back into fastboot mode and run..fastboot flashing unlock..
This WILL wipe your device :good:
Badger50 said:
Huh?? If you want to unlock it, make sure OEM unlocking and USB debugging is turned on in developer options. Then go back into fastboot mode and run..fastboot flashing unlock..
This WILL wipe your device :good:
Click to expand...
Click to collapse
I've tried unlocked bootloader, give same error
Sent from my Pixel 4 XL using Tapatalk
thatotherguy.. said:
I've tried unlocked bootloader, give same error
Click to expand...
Click to collapse
Then, maybe you have a carrier bootloader locked device??
When trying to update I get the following error. I have attempted multiple updates thinking maybe I had to do some incremental ones before doing the most recent. rq1a.201205.008.zip is the oldest one that fails and all the more recent ones do also.
Code:
C:\platform-tools>flash-all
Sending 'bootloader' (8825 KB) OKAY [ 0.044s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.004s
< waiting for any device >
Sending 'radio_b' (82692 KB) OKAY [ 0.458s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g8150-00075-201008-B-6891495
(bootloader) Flashing partition modem_b
OKAY [ 0.607s]
Finished. Total time: 1.634s
Rebooting into bootloader OKAY [ 0.041s]
Finished. Total time: 0.053s
--------------------------------------------
Bootloader Version...: c2f2-0.3-6648663
Baseband Version.....: g8150-00075-201008-B-6891495
Serial Number........: xxxxxxxxxxxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.062s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'c2f2-0.3-6648663'.
Update requires 'c2f2-0.3-6863466'.
fastboot: error: requirements not met!
Press any key to exit...
sabindaman said:
When trying to update I get the following error. I have attempted multiple updates thinking maybe I had to do some incremental ones before doing the most recent. rq1a.201205.008.zip is the oldest one that fails and all the more recent ones do also.
Code:
C:\platform-tools>flash-all
Sending 'bootloader' (8825 KB) OKAY [ 0.044s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.004s
< waiting for any device >
Sending 'radio_b' (82692 KB) OKAY [ 0.458s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g8150-00075-201008-B-6891495
(bootloader) Flashing partition modem_b
OKAY [ 0.607s]
Finished. Total time: 1.634s
Rebooting into bootloader OKAY [ 0.041s]
Finished. Total time: 0.053s
--------------------------------------------
Bootloader Version...: c2f2-0.3-6648663
Baseband Version.....: g8150-00075-201008-B-6891495
Serial Number........: xxxxxxxxxxxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.062s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'c2f2-0.3-6648663'.
Update requires 'c2f2-0.3-6863466'.
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse
Are these the files in your platform tools? (These are from Jan. 2021 factory image). Also, are your platform tools up to date?
Lughnasadh said:
Are these the files in your platform tools? (These are from Jan. 2021 factory image). Also, are your platform tools up to date?
Click to expand...
Click to collapse
Yeah. they are all in there. I've done 3 other updates successfully and not had any issues. But when I try the January one or the previous 2 updates they all fail to flash the bootloader at the beginning and give me the same error about the bootloader version later on and abort the update.
platform tools is r30.0.5 which is most current as far as I can find
sabindaman said:
Yeah. they are all in there. I've done 3 other updates successfully and not had any issues. But when I try the January one or the previous 2 updates they all fail to flash the bootloader at the beginning and give me the same error about the bootloader version later on and abort the update.
platform tools is r30.0.5 which is most current as far as I can find
Click to expand...
Click to collapse
Do, are you saying you are on October update?
Jan, Dec, Nov don't install?
Tulsadiver said:
Do, are you saying you are on October update?
Jan, Dec, Nov don't install?
Click to expand...
Click to collapse
RP1A.201105.002 is the version I am running and most recent one that would successfully install.
sabindaman said:
RP1A.201105.002 is the version I am running and most recent one that would successfully install.
Click to expand...
Click to collapse
Have you tried installing your bootloader manually?
fastboot flash bootloader bootloader-coral-c2f2-0.3-6863466.img
Tulsadiver said:
Have you tried installing your bootloader manually?
fastboot flash bootloader bootloader-coral-c2f2-0.3-6863466.img
Click to expand...
Click to collapse
No luck
I don't know if it matters but on fastboot it has secure boot: yes while on the bootloader it has device state as unlocked
Code:
C:\platform-tools>fastboot flash bootloader bootloader-coral-c2f2-0.3-6863466.img
Sending 'bootloader' (8825 KB) OKAY [ 0.053s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
C:\platform-tools>
sabindaman said:
No luck
I don't know if it matters but on fastboot it has secure boot: yes while on the bootloader it has device state as unlocked
Code:
C:\platform-tools>fastboot flash bootloader bootloader-coral-c2f2-0.3-6863466.img
Sending 'bootloader' (8825 KB) OKAY [ 0.053s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
C:\platform-tools>
Click to expand...
Click to collapse
Have you tried settings/system/system update?
Maybe change slot to "a" and try it there?
Just throwing some things out there.
Tulsadiver said:
Have you tried settings/system/system update?
Maybe change slot to "a" and try it there?
Just throwing some things out there.
Click to expand...
Click to collapse
Well after a few days of checking system update it finally decided the December update existed and it would download it. At which put it into the most recent bootloader version. Thanks for help.
sabindaman said:
Well after a few days of checking system update it finally decided the December update existed and it would download it. At which put it into the most recent bootloader version. Thanks for help.
Click to expand...
Click to collapse
Great!
sabindaman said:
When trying to update I get the following error. I have attempted multiple updates thinking maybe I had to do some incremental ones before doing the most recent. rq1a.201205.008.zip is the oldest one that fails and all the more recent ones do also.
Code:
C:\platform-tools>flash-all
Sending 'bootloader' (8825 KB) OKAY [ 0.044s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.004s
< waiting for any device >
Sending 'radio_b' (82692 KB) OKAY [ 0.458s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g8150-00075-201008-B-6891495
(bootloader) Flashing partition modem_b
OKAY [ 0.607s]
Finished. Total time: 1.634s
Rebooting into bootloader OKAY [ 0.041s]
Finished. Total time: 0.053s
--------------------------------------------
Bootloader Version...: c2f2-0.3-6648663
Baseband Version.....: g8150-00075-201008-B-6891495
Serial Number........: xxxxxxxxxxxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.062s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'c2f2-0.3-6648663'.
Update requires 'c2f2-0.3-6863466'.
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse
Your bootloader is locked.
Here are a few commands to solve this problem. All you have to do is unlock the bootloader and after that you can flash your Google Pixel phone with any version.
1. https://download.highonandroid.com/file/Tools
download fastboot.zip
extract and open Command Prompt to this folder (Ctrl+Shift+right click mous button)
2.
To unlock the bootloader and enable partitions to be reflashed, run the
"fastboot flashing unlock" command (without quotes) on the device.
3. And running the "fastboot flashing unlock" command (without quotes) but requires the user to press a physical button on the device.That is ALLL. Francuz Barajevo
I had my bootloader unlocked and I still had the same issue.
The solution? Simply run the script again. When you get this error, the phone will be on the fastboot screen. Just run the script again and this time it will flash the new bootloader, reboot itself and then continue the process.
Good luck!
(for me, this happened on a Pixel 4a, while flashing the 2021 September update)
Lughnasadh said:
Are these the files in your platform tools? (These are from Jan. 2021 factory image). Also, are your platform tools up to date?
Click to expand...
Click to collapse
I don't have them. Where can I find them?
N-Gage4ever said:
I don't have them. Where can I find them?
Click to expand...
Click to collapse
Factory images
Platform Tools
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.615s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.615s
Stuck in FASTBOOT ...
Flash fastboot ROM
Setting current slot to 'a' OKAY [ 12.421s]
Finished. Total time: 12.517s
Rebooting OKAY [ 0.098s]
Finished. Total time: 3.115s
Rebooting, then back to FASTBOOT
Solved!!
I got help from Xiaomi support
Helen17 said:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.615s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.615s
Stuck in FASTBOOT ...
Click to expand...
Click to collapse
i had the exact same problem, but someone on the site has solved the problem and repaired my phone on distance but against fee, if you want i can send you the link for him.
Helen17 said:
Solved!!
I got help from Xiaomi support
Click to expand...
Click to collapse
how to solved?