Develop Bugs

Can't Flash TWRP "Signature Verify Fail"

This is an ATT version phone I rooted this phone a couple of days ago with TWRP. However, I had to use adb to enter fastboot as it would not go to fastboot using power/volume keys. Actually, it never shows a fastboot screen, even in adb, so it may have been going into fastboot all along and I just could not see it.
So, instead of leaving well enough alone, I RUU'ed (newest ATT version from HTC site) it to try to get fastboot to work normally (it still works, I just can't see it on screen). Now, I can't get rooted again. FWIW, I did make a backup with TWRP before RUU'ed. Regardless, there is nothing on this phone I need to keep, I just want to root it before I start using it.
Any help is greatly appreciated...
Here is my unlock sequence. Note what happens if I try to flash TWRP immediately after unlock. I have to CTRL C and Reboot phone.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash unlockt
oken unlock_code.bin
target reported max download size of 1826414592 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.110s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.012s]
finished. total time: 0.125s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
Now when I try to flash TWRP, I get :
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recover' (20022 KB)...
OKAY [ 1.884s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.611s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
HT445####### fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.013s

Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.

Mr Hofs said:
Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.
Click to expand...
Click to collapse
Same Results:
C:\s>fastboot flash recovery twrpm8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.438s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.976s
C:\s>
C:\s>fastboot flash recovery twrp30m8
error: cannot load 'twrp30m8'
C:\s>fastboot flash recovery twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.889s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.616s
C:\s>

Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.

Mr Hofs said:
Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.
Click to expand...
Click to collapse
Already tried that, but tried again. First below is my result before I downloaded new twrp and the second one is my result after I re-downloaded image
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.896s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.899s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>

Try the HTC_fastboot adb package. It's posted several times here on xda.

Mr Hofs said:
Try the HTC_fastboot adb package. It's posted several times here on xda.
Click to expand...
Click to collapse
Still no luck, same error (see below). This worked flawless before I flashed the latest ATT RUU.
Is it possible phone is still not unlocked or would I be getting that far if it was still locked?
Question. This phone is AT&T (more details in getvar above) but at the end of the contract, AT&T sent me code to unlock the SIM. Now, the SIM I am using is on a T-Mobile MVNO (TING). Since they SIM unlocked the phone, would I be able to and would there be any advantage/risk to trying to flash the Stock RUU for HTC unlocked/developer. It is a higher software version than the ATT version I flashed (twice).
C:\FB>htc_fastboot flash recovery twrp.img
sending 'recovery' (20022 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Execution time is 3(s)

Any other ideas? I can't see bootloader screen, but it appears I can access and do all bootloader functions in adb.
I would really like to be able to eliminate locked bootloader as the issue, is there anything else I can flash or try that might let me know if bootloader is still locked. I can get results from getvar and fastboot devices.
I also have an image of the phone saved from TWRP before I flashed the RUU, but seems no way to get that image back. I am not opposed to purchasing S-off if that will for sure help me.

Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html

joikep said:
Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html
Click to expand...
Click to collapse
Already tried two previous versions

rockfordpi said:
Already tried two previous versions
Click to expand...
Click to collapse
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?

rockfordpi said:
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?
Click to expand...
Click to collapse
OK, we can close this one out. I did want to post my solution, just in case anyone else had a similar error.
Long Story a little bit shorter, on my HTC one M8, the error:
sending 'recovery' (11976 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Was due to a locked bootloader. Because, for some reason I can't see the bootloader on my phone, I could not see the lock status, so I was having to do EVERYTHING via ADB. The problem was, when unlocking the bootloader there is screen on the phone that asks you to confirm yes or no if you want to unlock it. I could not see that screen and the instructions I was reading left that out (It was a good assumption that if one was trying to unlock one would know to say YES. LOL). So, I was missing that step. When I found that step, even though I could not see it on screen, I just blindly pushed volume down and then power to select. At that point it unlocked and allowed me to flash twrp 3.0.
Still do not know WHY I can't see the bootloader screen. I wonder if for some reason the colors are off in my bootloader screen and all the words are the same color as the background or it is trying to redirect that output somewhere else.
but at this point I am going to live with it as trying to fix it is what got me in here in the first place.

Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Someone have an idea to help me ?
Many thanks

foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
Click to expand...
Click to collapse
The top post is in regards to getting signature verify fail message when flashing custom recovery. So I don't see how it's the "same problem".
Be careful about saying "same problem" without giving any specific information about your actual problem, or device details. From my experience, I've seen many dozens of times where folks say they have the "same problem" and when prompted for more info, we find there are many many differences.
foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
Click to expand...
Click to collapse
Did the RUU flash successfully, or were there any error messages?
Also, please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the phone.
foosee said:
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Click to expand...
Click to collapse
This is normal and expected. You can't use adb when in bootloader. And you can't use fastboot and adb simultaneously. Meaning, when one works, the other will not work, by definition.
Fastboot = only works in bootloader fastboot mode
adb = only works within OS, or alternately will work in custom recovery TWRP
If you issue the command fastboot devices, you should find that it works.
It is also not clear what you are trying to use adb to do (what commands?).

ZE551ML No bootloader, blackscreen after colored logo on xFSKT

Good night everyone.
I got my zenfone 2 (ZE551ML) bricked after trying to upgrade cm14. I can do xFSTK just fine, but next i got this:
I have a blackscreen after the 4 colour screen, instead of bootloader. Then when i try the commands i got those errors:
fastboot oem erase_token
(bootloader) cmd_oem!arg= erase_token S
(bootloader) [0]erase_token S
FAILED (remote: Fail erase_token_umip)
finished. total time: 0.754s
fastboot oem partition /tmp/partition.tbl
(bootloader) cmd_oem!arg= partition /tmp/partition.tbl S
(bootloader) [0]partition S
(bootloader) [1]/tmp/partition.tbl S
FAILED (remote: GPT command failed
)
finished. total time: 0.773s
fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
FAILED (status read failed (Too many links))
finished. total time: 1.144s
The "Too many links" error is just for one time, if i try the command again it works, but others i cant get workaround
Any help? Is it really dead? :/

just flash raw file using Asus Flash Toll and it will work

Miguelkf said:
just flash raw file using Asus Flash Toll and it will work
Click to expand...
Click to collapse
I got the GPT error when flashing via Asus Flash Tool. And, if i check the log, others that i posted too.

so no hope for me :/

Trying to flash UK O2 HTC One M9

Hello, My phone recently started playing up and it's out of warranty according to O2 because of a scratch on the screen.
The problem was settings would not open, with "Unfortunately settings has stopped". Next the same thing happened to the play store so I can't change any settings or install any apps. Great.
I tried a few suggestions online:
- Wiped cache in bootloader.
- Factory reset
Neither solve the problem, the same error still happens on a fresh install.
So that gets me thinking I need to reinstall firmware? Please tell me to STOP now if this is the wrong thing to do!
I've not done this before so forgive my noobiness.
I've located the correct RUU I believe matching these details:
Code:
C:\Users\Ed\Downloads\ADB_20151221_Fastboot_20150822_HtcFastboot_20150529>fastboot getvar all (bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: ############
(bootloader) version-main: 3.35.206.13
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_93.00.51117G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: O2___001
all:
finished. total time: 0.017s
androidfilehost fid=24421527759889318
This is what I've got (sorry can't post links!).
I don't have an SD card to fit the phone, can I flash this from my PC or do I need an EXE version?
Thanks
Ed
EDIT: On download of that RUU zip file, when I try to extract the files it says archive corrupt (I've tried downloading twice). Is that normal or is the thing broken? Don't wanna brick the phone.

You don't have to extract the zip file. It's normal for the zip file to not be openable/extractable, as it's encrypted. If you *really* need access to the inside of the RUU (example, get the stock boot image), use the Universal Decryption Tool.
I'm not 100% sure, but I think you should reflash the firmware. Although it's optional, I think your bootloader should be LOCKED or RELOCKED before flashing your RUU.
Instructions are here.
And remember, just in case, triple-check your RUUs.

lazyguyMC said:
You don't have to extract the zip file. It's normal for the zip file to not be openable/extractable, as it's encrypted. If you *really* need access to the inside of the RUU (example, get the stock boot image), use the Universal Decryption Tool.
I'm not 100% sure, but I think you should reflash the firmware. Although it's optional, I think your bootloader should be LOCKED or RELOCKED before flashing your RUU.
Instructions are here.
And remember, just in case, triple-check your RUUs.
Click to expand...
Click to collapse
As I said I don't have an SD card which is all the instructions that post gives, however I found a guide for htc_fastboot. I tried with locked and unlocked. Here is the output:
C:\Users\Ed\Downloads\ADB_20151221_Fastboot_20150822_HtcFastboot_20150529>htc_fastboot oem rebootRUU ...
OKAY [ 0.056s]
finished. total time: 0.056s
htc_fastboot finished. total time: 0.284s
C:\Users\Ed\Downloads\ADB_20151221_Fastboot_20150822_HtcFastboot_20150529>htc_fastboot flash zip 0PJAIMG.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.35.206.13
found large-zip header, file count: 8
processing file 1/8...
sending 'zip' (159355 KB)...
OKAY [ 9.158s]
writing 'zip'...
(bootloader) HOSD CL#670363
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 13.808s
preupdate done, rebooting...
resending command...
< waiting for device >
sending 'zip' (159355 KB)...
FAILED (status read failed (Unknown error))
finished. total time: 9.218s
htc_fastboot finished. total time: 41.721s
C:\Users\Ed\Downloads\ADB_20151221_Fastboot_20150822_HtcFastboot_20150529>htc_fastboot oem rebootRUU ...
OKAY [ 0.001s]
finished. total time: 0.001s
htc_fastboot finished. total time: 0.218s
C:\Users\Ed\Downloads\ADB_20151221_Fastboot_20150822_HtcFastboot_20150529>htc_fastboot flash zip 0PJAIMG.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.35.206.13
found large-zip header, file count: 8
processing file 1/8...
< waiting for device >
sending 'zip' (159355 KB)...
FAILED (status read failed (Unknown error))
finished. total time: 9.194s
htc_fastboot finished. total time:
25.078s
C:\Users\Ed\Downloads\ADB_20151221_Fastboot_20150822_HtcFastboot_20150529>htc_fastboot oem unlock ...
OKAY [ 0.000s]
finished. total time: 0.000s
htc_fastboot finished. total time: 0.206s
C:\Users\Ed\Downloads\ADB_20151221_Fastboot_20150822_HtcFastboot_20150529>htc_fastboot oem rebootRUU ...
OKAY [ 0.001s]
finished. total time: 0.001s
htc_fastboot finished. total time: 0.194s
C:\Users\Ed\Downloads\ADB_20151221_Fastboot_20150822_HtcFastboot_20150529>htc_fastboot flash zip 0PJAIMG.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.35.206.13
found large-zip header, file count: 8
processing file 1/8...
< waiting for device >
sending 'zip' (159355 KB)...
FAILED (status read failed (Unknown error))
finished. total time: 9.309s
htc_fastboot finished. total time: 23.830s
Click to expand...
Click to collapse
Neither seems to be working. At the moment the phone is still in RUU mode with the a progress bar about 20% on blue. Don't want to switch it off midway?!
EDIT: To be exact it fails at 18% in the second phase (after pre-update).

I can't help much, but you should try using a regular fastboot.exe and change "htc_fastboot" to "fastboot" in your commands(don't. it will fail.) Also try checking here.

boblettoj99 said:
As I said I don't have an SD card which is all the instructions that post gives, however I found a guide for htc_fastboot. I tried with locked and unlocked. Here is the output:
Neither seems to be working. At the moment the phone is still in RUU mode with the a progress bar about 20% on blue. Don't want to switch it off midway?!
EDIT: To be exact it fails at 18% in the second phase (after pre-update).
Click to expand...
Click to collapse
Wizard_RUU​
A small utility from HTC - a shell for flashing RUU.zip through PC (Windows)
Unpacked and taken from official RUU.exe from HTC
How to use:
Download archive Wizard_RUU.rar, unpack.
Download the stock RUU firmware in ZIP (suitable for CID and MID of your phone)
Copy the stock RUU ZIP in the folder with Wizard_RUU
Rename 0PJAIMG_HIMA _ *****. zip to rom.zip
Run the ARUWizard.exe file and follow the on-screen instructions.
If after installing ARUWizard.exe and after confirming the agreement condition, the installation crashes, then download and install Microsoft Visual C ++. After that, run ARUWizard.exe again
Download:
Wizard_RUU.rar (mirror on AFH)
It is used as an alternative to installing the ruu.zip through an external sd card.
PS. All data on the phone will be deleted. If possible, make a backup before installing RUU.

OMG - i bricked my three.co.uk phone.

I have searched and searched but cannot find anywhere that tells me what these messages mean in fastboot.
Example:
(bootloader) has-slot:bootloader: not found
(bootloader) is-logical:bootloader: not found
Please help.
Thank you.

Did you do something before this happened?

LOL, yes, I completely fecked it up.
I have got the recovery back now, but when I try to flash a stock image,
1. Obviously will not flash the bootloader cos it is now unlocked. So I deleted the bits in the bat file that try to flash the bootloader so that the rest can complete.
2. Now will only get to various Systemchunks and then hangs, having installed previous system chunks ok.
Seems to get to here and then hangs.
Executing ".\Windows\fastboot.exe -s SERIALNUMBER flash system systemchunk10.img"
target max-download-size: 512MB
sending 'system' (262143 KB)...
I though about erasing system, butbut the I now get this message bootloader message.
fastboot erase system
(bootloader) has-slot:system: not found
Erasing 'system' OKAY [ 0.025s]
Finished. Total time: 0.062s
So, I had to go to Qualcomm fix, and I have lineage 16 on it now, but I have lost my IMEI's
Thanks for reading.

myjess said:
LOL, yes, I completely fecked it up.
I have got the recovery back now, but when I try to flash a stock image,
1. Obviously will not flash the bootloader cos it is now unlocked. So I deleted the bits in the bat file that try to flash the bootloader so that the rest can complete.
2. Now will only get to various Systemchunks and then hangs, having installed previous system chunks ok.
Seems to get to here and then hangs.
Executing ".\Windows\fastboot.exe -s SERIALNUMBER flash system systemchunk10.img"
target max-download-size: 512MB
sending 'system' (262143 KB)...
I though about erasing system, butbut the I now get this message bootloader message.
fastboot erase system
(bootloader) has-slot:system: not found
Erasing 'system' OKAY [ 0.025s]
Finished. Total time: 0.062s
So, I had to go to Qualcomm fix, and I have lineage 16 on it now, but I have lost my IMEI's
Thanks for reading.
Click to expand...
Click to collapse
probably u just delete system image file

Is ok, got it all working again.
Thanks.

XT1670 revert to stock issue

SOLVED I will make a topic about it https://forum.xda-developers.com/g5/help/how-to-revert-moto-g5-xt1670-to-stock-t4183425
Hello, how are you all over there? I here in trouble with this XT1670. I have installed several roms but now i want to go back to the official one, but it dont lock the bootloader.
Tried the following command (twice) to lock the bootloader: fastboot oem lock
And i get the following result:
Code:
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.016s]
finished. total time: 0.016s
Now i use the following command: fastboot flash boot boot.img
And the following was obtained:
Code:
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB) ...
OKAY [0.545s]
writing 'boot' ...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.747s
I have already tried several. Boot, gpt, oem with official rom. All showing the error "Security version downgrade"
I also tried Lenovo's Rescue & Smart app, but it says the SKU is wrong and doesn't recognize the mobile phone.
I don't know how to continue. I could put an official rom, but when you restart the phone the bootloader appears. It only starts when press start.
Not only does that happen. Every so often, the phone turns itself off and remains in the bootloader. And then when you start up, bug reports pop up to share with who knows what.
I do not know what to do. You are the experts.
Ty in advance