Database Develop

HELP - BRICKED One!

I was flashing a new rom onto my HTC One today and my daughter got hold of it (Age 3) whilst my back was turned and has wiped the ROM completely!
I have TWRP v2.7.1.1 touch bootloader but I cant get a ROM installed - fastboot won't recognise that there is a device attached even though I get the 'connected sound' when I connect to my windows 8 laptop. I have searched for all the fastboot and adb solutions but have come to a dead end!
I think its dead! :crying:
Fastboot usb shows on the phone screen when connected though
the OS - on the fastboot screen shows blank too!
*** TAMPERED ***
*** RELOCKED ***
M7_ PVT SHIP S_ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 21 2013,22:50:54.0
Can anyone help?

lol if you have a working recovery then your device is not bricked. Even if your recovery is broken if you can access the bootloader your device is still fine.
It sounds to me like you are having some trouble with the windows drivers.. if you have a pc with linux I would try it there as it is easier. or if you only have win8 then you have to install these drivers http://forum.xda-developers.com/showthread.php?t=2544146
btw what problem do you have when installing the rom via recovery?

cuyo11 said:
lol if you have a working recovery then your device is not bricked. Even if your recovery is broken if you can access the bootloader your device is still fine.
It sounds to me like you are having some trouble with the windows drivers.. if you have a pc with linux I would try it there as it is easier. or if you only have win8 then you have to install these drivers http://forum.xda-developers.com/showthread.php?t=2544146
btw what problem do you have when installing the rom via recovery?
Click to expand...
Click to collapse
"C:\android-tools>fastboot devices
HT34PW913345 fastboot"​
CID = HTC__001
I can attempt to flash a .zip rom (same recovery number = stock 5.11.401.10) but it fails!
C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 43.432s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 179.412s​
I cant flash a different recovery anymore I presume as my bootloader is "RELOCKED" and I can't work out how to unlock it. HTCDev can't unlock it.
C:\android-tools>fastboot flash recovery recovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.187s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.141s​
What is "bootloader signature checking"? How do I resolve that problem of FAILED?
I can access the RUU screen successfully
[INDENTC:\android-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.187s]
finished. total time: 0.234s][/INDENT]
but when I try to flash a .zip it doesn't work still
C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 44.000s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 159.127s​
Anyone have any ideas of how to get the signature checking to work?

I have managed to unlock again using my Unlock_code.bin file but it still fails to load the .zip ROM
C:\android-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.016s]
finished. total time: 0.172s
C:\android-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.172s
C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 43.874s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.203s​

I have now managed to load ClockworkMod Recovery v6.0.4.6
I have found I can't mount the /sdcard
I guess that's where my problem lies? If my phone has forgotten how to find /sdcard then how can it flash to it?

targett said:
I have now managed to load ClockworkMod Recovery v6.0.4.6
I have found I can't mount the /sdcard
I guess that's where my problem lies? If my phone has forgotten how to find /sdcard then how can it flash to it?
Click to expand...
Click to collapse
Check this http://forum.xda-developers.com/showthread.php?t=2228274&page=3
then let me know if you have any questions.

nkk71 said:
Check this http://forum.xda-developers.com/showthread.php?t=2228274&page=3
then let me know if you have any questions.
Click to expand...
Click to collapse
I have wiped the system and cache just in case and am attempting the sideload but when i do the "adb devices" it doesn't sow my device number, where it does if in fastboot.
G:\adb>adb devices
List of devices attached
​
And when I attempt at adb sideload I get this
G:\adb>adb sideload One_5.11.401.10_odexed.zip
error: device not found​Stuck again :crying:
Oh - How important is the USB OTG in the adb sideload

targett said:
I have wiped the system and cache just in case and am attempting the sideload but when i do the "adb devices" it doesn't sow my device number, where it does if in fastboot.
Stuck again:crying:
Click to expand...
Click to collapse
it is mentioned in the post, but here again: FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

nkk71 said:
it is mentioned in the post, but here again: FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
Sorry for being so stupid! I feel like a noob on this device (not flashed or rooted in about 3 years!)
Reading it all again I see I need S-Off. My Security is ON. and I can't turn it off as I can't install SuperSU or Superuser or anything at all.
Any thoughts?

targett said:
Sorry for being so stupid! I feel like a noob on this device (not flashed or rooted in about 3 years!)
Reading it all again I see I need S-Off. My Security is ON. and I can't turn it off as I can't install SuperSU or Superuser or anything at all.
Any thoughts?
Click to expand...
Click to collapse
sorry, i don't follow. it has nothing to do with s-on or s-off.
you say your device isn't being seen while in custom recovery, but it has to show somewhere in device manager, no? if yes, then you may need to manually select the correct drivers, that's it

nkk71 said:
sorry, i don't follow. it has nothing to do with s-on or s-off.
you say your device isn't being seen while in custom recovery, but it has to show somewhere in device manager, no? if yes, then you may need to manually select the correct drivers, that's it
Click to expand...
Click to collapse
Sorry!
I have sorted the Win8 driver issue - Hadn't spotted that one.
I have now managed to adb push the .zip file and adb sideload it too.
I'm now installing the 'sideload.zip' Wish me luck!
Wordked! It F#*king WORKED!!!!!
Thank you, thank you, thank you!

targett said:
Sorry!
I have sorted the Win8 driver issue - Hadn't spotted that one.
I have now managed to adb push the .zip file and adb sideload it too.
I'm now installing the 'sideload.zip' Wish me luck!
Wordked! It F#*king WORKED!!!!!
Thank you, thank you, thank you!
Click to expand...
Click to collapse
Good Luck :good: :good:

[Q] XT1095 fastboot flash system.img failed

Hey,guys! I uesd fastboot to flash system,but it failed
code:
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.040s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.249s
anyone can help me please?

YOUNG MAN. said:
Hey,guys! I uesd fastboot to flash system,but it failed
code:
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.040s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.249s
anyone can help me please?
Click to expand...
Click to collapse
Try to use the mfastboot, because the system.img is to big to use the normal fastboot

libnijunior said:
Try to use the mfastboot, because the system.img is to big to use the normal fastboot
Click to expand...
Click to collapse
it failed too
code
target reported max download size of 536870912 bytes
sending 'system' (256089 KB)...
OKAY [ 8.035s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.062s
and sometimes it shows
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.046s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.224s

YOUNG MAN. said:
it failed too
code
target reported max download size of 536870912 bytes
sending 'system' (256089 KB)...
OKAY [ 8.035s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.062s
and sometimes it shows
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.046s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.224s
Click to expand...
Click to collapse
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.

juliospinoza said:
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.
Click to expand...
Click to collapse
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.
Do you have any way to solve this problem? My phone is bootloop now.
Thanx

YOUNG MAN. said:
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.
Do you have any way to solve this problem? My phone is bootloop now.
Thanx
Click to expand...
Click to collapse
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?

JulesJam said:
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
Click to expand...
Click to collapse
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?

YOUNG MAN. said:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
Click to expand...
Click to collapse
Yes, they are synonyms. I would install Motorola Device Manager to your PC and let it attempt to repair your phone.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
If it doesn't repair your phone, post back here.

YOUNG MAN. said:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
Click to expand...
Click to collapse
I installed Motorola Device Manager, what should i do next?

JulesJam said:
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
Click to expand...
Click to collapse
I installed Motorola Device Manager and tried again, it still did't work.
code:
C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk
.0
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.047s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.217s

YOUNG MAN. said:
I installed Motorola Device Manager and tried again, it still did't work.
Click to expand...
Click to collapse
Did it detect your device at all? Did it try to repair it?
YOUNG MAN. said:
C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk
.0
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.047s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.217s
Click to expand...
Click to collapse
If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?
http://rootjunkysdl.com/?device=Adb Fastboot Files

Go into developer options and enable OEM unlocking. Then try it.
Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?
Sent from my XT1095

JulesJam said:
Did it detect your device at all? Did it try to repair it?
If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?
Click to expand...
Click to collapse
NO,It not detect my phone,it just search new software when i open it.
And I tried the latest version of fastboot,still failed

YOUNG MAN. said:
NO,It not detect my phone,it just search new software when i open it.
And I tried the latest version of fastboot,still failed
Click to expand...
Click to collapse
Did you try RSDLite?

JulesJam said:
Did you try RSDLite?
Click to expand...
Click to collapse
it can't detect my phone

YOUNG MAN. said:
it can't detect my phone
Click to expand...
Click to collapse
When you are in recovery, what does
adb devices
show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.

JulesJam said:
When you are in recovery, what does
adb devices
show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.
Click to expand...
Click to collapse
it shows View attachment 3294009
but in fastboot mode it shows View attachment 3294012
and my recovery is TWRP 2.8.60

YOUNG MAN. said:
it shows View attachment 3294009
but in fastboot mode it shows View attachment 3294012
and my recovery is TWRP 2.8.60
Click to expand...
Click to collapse
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]
then when you are at the proper directory, at the command prompt in the command window type:
adb devices
then hit enter.
It should return the serial number of your device.

JulesJam said:
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]
then when you are at the proper directory, at the command prompt in the command window type:
adb devices
then hit enter.
It should return the serial number of your device.
Click to expand...
Click to collapse
it shows this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
device

dustin_b said:
Go into developer options and enable OEM unlocking. Then try it.
Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?
Sent from my XT1095
Click to expand...
Click to collapse
NO,my recovery is TWRP now ,and I can't flash the original recovery ,it failed.

Huawei phone bricked. pls help me

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.

Unable to update

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

Pixel 5 after OTA update can't start, stuck fastboot mode

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?