Hi!
Why I got the following error:
C:\Users\myuser\Downloads\sdk\tools>fastboot flash radio radio.img
sending 'radio' (21376 KB)... OKAY
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
Best Regards,
Thanks a lot
A.
Did you resolve this? I get the same error on my HTC Legend.
I've been trying to flash a stock recovery or CWM Touch onto my HTC One using fastboot.exe that came with the latest version of ADK.
This is what happened:
sending 'recovery' (9480 KB)...
OKAY [ 1.096s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.630s
Please help. I've looked upon at least 30 websites, including xda-developers.Thanks!
Why don't you just flash it through the app? Or flash twrp through goo manager. It's also touch based.
mr_verystock said:
I've been trying to flash a stock recovery or CWM Touch onto my HTC One using fastboot.exe that came with the latest version of ADK.
This is what happened:
sending 'recovery' (9480 KB)...
OKAY [ 1.096s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.630s
Please help. I've looked upon at least 30 websites, including xda-developers.Thanks!
Click to expand...
Click to collapse
Redownload the image.
mr_verystock said:
I've been trying to flash a stock recovery or CWM Touch onto my HTC One using fastboot.exe that came with the latest version of ADK.
This is what happened:
sending 'recovery' (9480 KB)...
OKAY [ 1.096s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.630s
Please help. I've looked upon at least 30 websites, including xda-developers.Thanks!
Click to expand...
Click to collapse
It sounds like your bootloader is still locked. Unlock it through htcdev before trying to fastboot flash recovery.
Sent from my HTC One S using Tapatalk 2
So I downloaded this Archive.zip from http://forum.xda-developers.com/showthread.php?t=2064868
and I boot my device to fastboot...
now on my pc when i type:
fastboot flash recovery adsp.img
I get:
sending 'recovery' (6345 KB)...
OKAY [ 0.950s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 0.998s
--------------------------------------------------------
or if i try:
>fastboot flash adsp adsp.img
sending 'adsp' (6345 KB)...
OKAY [ 0.949s]
writing 'adsp'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.485s
What am I doing wrong? I have HBOOT-1.13 and viperones rom on my HTC One S
Im pretty sure you cant flash it through fastboot.
You need hboot 1.09 or lower and flash through recovery.
C:\Program Files\Android>fastboot flash unlock_token Unlock_code.bin
sending 'unlock_token' (0 KB)...
OKAY [ 0.141s]
writing 'unlock_token'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.156s
Anyone can help me with this? The problem arose after flashing twrp I ran RUU several times but it didn't help
Hi
Hope you are all doing great, I have limited experience from rooting my own phones, any help will be appreciated a lot.
After buying a pixel 2 (walleye/google store unlocked ) I wanted to root it like my other phones so I proceeded to unlock bootloader, temp boot twrp and installed magisk.
So far it was fine but gave me a notification that android has an internal error. So I decided to go back to stock and retry rooting. Flashed to stock was great. Set the phone up again, did not root it or anything from stock. When re-enabling the developer options & USB debugging I unfortunately locked boot loader up again.
The phone is stuck at bootloader ERROR: Slot Unbootable: Load Error, going to recovery it goes back to same.
Can't flash cos status locked, cant unlock .
Fastboot FAIL not allowed in locked state.
Download mode Error: Operation denied
Interestingly boot-slot is b, tried to change it , of course not allowed.
getvar all dump below, its what I could extract. Let me know if I can get you more info by running logging etc. that I can.
(bootloader) avb_err:0(0)
(bootloader) is_avb_critical_error:no
(bootloader) have_oem_lock_id:yes
(bootloader) avb_stored_rollback_indexes:
(bootloader) avb_user_settable_key_set:no
(bootloader) avb_version:1.0.
(bootloader) version-main:
(bootloader) imei:
(bootloader) boot-mode:FASTBOOT
(bootloader) logical-block-size:0x1000
(bootloader) erase-block-size:0x1000000
(bootloader) unlocked:no
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3759
(bootloader) version-baseband:g8998-00202-1803121407
(bootloader) version-bootloader:mw8998-002.0069.00
(bootloader) variant:
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xD49BFB000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x1F400000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x1F400000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xA0000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xA0000000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) has-slot:vbmeta:yes
(bootloader) has-slot:dtbo:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:1
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) cid:00000000
(bootloader) secure:yes
(bootloader) serialno:
(bootloader) hw-revision:MP1
(bootloader) product:walleye
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
all:
try flashing factory image again.
munchy_cool said:
try flashing factory image again.
Click to expand...
Click to collapse
Hi munchy_cool, first things first , thank you so much for taking out time to reply
I tried flashing stock again, I rechecked if I flashed the right stock (sometimes that is a problem)
----------------------------------------------------------
Sending 'bootloader_b' (38652 KB) OKAY [ 1.055s]
Writing 'bootloader_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.075s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.007s
Sending 'radio_b' (60412 KB) OKAY [ 1.657s]
Writing 'radio_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.672s
rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.007s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: mw8998-002.0069.00
Baseband Version.....: g8998-00202-1803121407
Serial Number........: XXXXXX
--------------------------------------------
Checking product OKAY [ 0.006s]
Checking version-bootloader FAILED
Device version-bootloader is 'mw8998-002.0069.00'.
Update requires 'mw8998-002.0067.00'.
fastboot: error: requirements not met!
Press any key to exit...
--------------------------------------------------------------
Then I tried with --slot to try to change it to a , no luck.
I rechecked the radio img and the bootimage but no luck
Try deuces script instead of stock script.
Worked for me
mrorange2108 said:
Try deuces script instead of stock script.
Worked for me
Click to expand...
Click to collapse
HI mrorange
thanks for your suggestion, I looked at deuces script, it does mention its for unlocked bootloader. Ran it anyway, all of it fails with FAILED (remote: Flashing is not allowed in Lock State) Rest of it is below. Any other suggestion that might help would be great.
--------------------------------------------------------------------
Deuces-flash-all-script-V4.5-Windows
for Taimen or Walleye - Google Pixel 2 / XL
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Unlock Bootloader[Y/N]?y
Running Unlock
Look at your device,
press up arrow and Power to confirm
FAILED (status read failed (Too many links))
Finished. Total time: 13.234s
This will say "failed" if already unlocked - ignore
Running Unlock_critical
Look at your device,
press up arrow and Power to confirm
FAILED (remote: unknown command)
Finished. Total time: 0.004s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
it is safe to ignore errors about active partition - there are multiple entries to support multiple versions of platform tools
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.013s
Sending 'bootloader_b' (38728 KB) OKAY [ 1.071s]
Writing 'bootloader_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.106s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
Sending 'radio_b' (60428 KB) OKAY [ 1.661s]
Writing 'radio_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.678s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.012s
Sending 'bootloader_b' (38728 KB) OKAY [ 1.059s]
Writing 'bootloader_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.078s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
Sending 'radio_b' (60428 KB) OKAY [ 1.657s]
Writing 'radio_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.678s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.012s
Sending 'abl_a' (404 KB) OKAY [ 0.027s]
Writing 'abl_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.048s
fastboot: error: cannot load 'aes.img': No such file or directory
Sending 'apdp_a' (16 KB) OKAY [ 0.016s]
Writing 'apdp_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.033s
Sending 'boot_a' (32768 KB) OKAY [ 0.909s]
Writing 'boot_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.929s
Sending 'cmnlib_a' (224 KB) OKAY [ 0.015s]
Writing 'cmnlib_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.035s
Sending 'cmnlib64_a' (292 KB) OKAY [ 0.025s]
Writing 'cmnlib64_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.045s
Sending 'devcfg_a' (60 KB) OKAY [ 0.015s]
Writing 'devcfg_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.037s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.228s]
Writing 'dtbo_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.248s
Sending 'hyp_a' (256 KB) OKAY [ 0.016s]
Writing 'hyp_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.036s
Sending 'keymaster_a' (280 KB) OKAY [ 0.019s]
Writing 'keymaster_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.040s
fastboot: error: cannot load 'laf.img': No such file or directory
Sending 'modem_a' (60420 KB) OKAY [ 1.640s]
Writing 'modem_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 1.658s
Sending 'msadp_a' (16 KB) OKAY [ 0.016s]
Writing 'msadp_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.039s
Sending 'pmic_a' (52 KB) OKAY [ 0.009s]
Writing 'pmic_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.029s
Sending 'rpm_a' (232 KB) OKAY [ 0.016s]
Writing 'rpm_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.039s
Sending 'tz_a' (1900 KB) OKAY [ 0.066s]
Writing 'tz_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.085s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.014s]
Writing 'vbmeta_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.034s
Sending 'vendor_a' (346964 KB) OKAY [ 9.482s]
Writing 'vendor_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 9.503s
Sending 'xbl_a' (3720 KB) OKAY [ 0.114s]
Writing 'xbl_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.136s
Flashing System A
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 16.225s]
Writing sparse 'system_a' 1/4 FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 29.095s
Flashing System B
Sending sparse 'system_b' 1/2 (524284 KB) OKAY [ 16.205s]
Writing sparse 'system_b' 1/2 FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 19.821s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.012s
Sending 'abl_b' (404 KB) OKAY [ 0.026s]
Writing 'abl_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.046s
fastboot: error: cannot load 'aes.img': No such file or directory
Sending 'apdp_b' (16 KB) OKAY [ 0.006s]
Writing 'apdp_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.026s
Sending 'boot_b' (32768 KB) OKAY [ 0.901s]
Writing 'boot_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.921s
Sending 'cmnlib_b' (224 KB) OKAY [ 0.019s]
Writing 'cmnlib_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.039s
Sending 'cmnlib64_b' (292 KB) OKAY [ 0.021s]
Writing 'cmnlib64_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.041s
Sending 'devcfg_b' (60 KB) OKAY [ 0.011s]
Writing 'devcfg_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.030s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.233s]
Writing 'dtbo_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.252s
Sending 'hyp_b' (256 KB) OKAY [ 0.015s]
Writing 'hyp_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.038s
Sending 'keymaster_b' (280 KB) OKAY [ 0.019s]
Writing 'keymaster_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.041s
fastboot: error: cannot load 'laf.img': No such file or directory
Sending 'modem_b' (60420 KB) OKAY [ 1.639s]
Writing 'modem_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 1.659s
Sending 'msadp_b' (16 KB) OKAY [ 0.013s]
Writing 'msadp_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.034s
Sending 'pmic_b' (52 KB) OKAY [ 0.010s]
Writing 'pmic_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.029s
Sending 'rpm_b' (232 KB) OKAY [ 0.017s]
Writing 'rpm_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.037s
Sending 'tz_b' (1900 KB) OKAY [ 0.063s]
Writing 'tz_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.085s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.011s]
Writing 'vbmeta_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.031s
Sending 'vendor_b' (346964 KB) OKAY [ 9.583s]
Writing 'vendor_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 9.604s
Sending 'xbl_b' (3720 KB) OKAY [ 0.109s]
Writing 'xbl_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.132s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.012s
Format Userdata[Y/N]?y
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 13933563 4k blocks and 3489792 inodes
Filesystem UUID: XXXXXXX
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4497 KB) OKAY [ 0.138s]
Writing 'userdata' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.656s
NoobHelp said:
HI mrorange
thanks for your suggestion, I looked at deuces script, it does mention its for unlocked bootloader. Ran it anyway, all of it fails with FAILED (remote: Flashing is not allowed in Lock State) Rest of it is below. Any other suggestion that might help would be great.
Click to expand...
Click to collapse
Surely there is a way to fix this? My getvar returned nearly identical information, except that my slots were all successful.
Did you have any luck with this or know anyone that has?
Thanks,
Alex