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?).

Wrong Bootloader Unlock key

Hello, Im trying to open my bootloader and having a lot of trouble with it, at first, I had a problem with LG, when I tried to get my unlock.bin file, it said that the device id and imei does not match, I guessed it was because I had my motherboard replaced(twice..) and emailed LG developer support, they helped me and I managed to download the unlock.bin file, but then when I tried to flash it I get the next error:
G:\Program Files\Minimal ADB and Fastboot>fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.017s]
writing 'unlock'...
(bootloader) -----------------------------------------------------------
(bootloader) Error!!
(bootloader) Wrong Bootloader Unlock key
(bootloader) -----------------------------------------------------------
FAILED (remote failure)
finished. total time: 0.125s
I did make sure that the unlock.bin file I downloaded is in the same folder as the adb, but nothing works..
Thanks for the help.

Rollback to stock failed.

The bootloader are unlocked. But, when I decide to rollback, I started the flash process using "fastboot oem lock begin"; then, every try of flash give me this kind of error, showed bellow.
So, for example, I got this when I tried to flash stock over a lineage rom:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.014s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.184s
What should I do? I have tried to flash bootloader.img and use "fastboot oem fb_mode_set", but stay in the same situation.
Obviously, I'm using the exactly stock versions to my device.
Thank you guys! :laugh:

motafoca55 said:
The bootloader are unlocked. But, when I decide to rollback, I started the flash process using "fastboot oem lock begin"; then, every try of flash give me this kind of error, showed bellow.
So, for example, I got this when I tried to flash stock over a lineage rom:
What should I do? I have tried to flash bootloader.img and use "fastboot oem fb_mode_set", but stay in the same situation.
Obviously, I'm using the exactly stock versions to my device.
Thank you guys! :laugh:
Click to expand...
Click to collapse
All I can say is you should have pulled ur stock ROM

Cant flash recovery error target reported max download size of 536870912 by

I can't flash my recovery.
Bootloader is unlocked.
Phone is not rooted
This sucks becouse i bought this phone thinking i whould not have this ****ing problem again.
(also lost my old one for the millionth time)
PS C:\Users\Admin> fastboot flash recovery C:\ProgramData\chocolatey\lib\adb\tools\platform-tools\twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.473s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.502s
PS C:\Users\Admin>
Click to expand...
Click to collapse

Weird, that validation error is usually shown when bootloader isn't actually unlocked. Have you tried unlocking it again? Have you tried with mfastboot?

DrunkenPanda2000 said:
I can't flash my recovery.
Bootloader is unlocked.
Phone is not rooted
This sucks becouse i bought this phone thinking i whould not have this ****ing problem again.
(also lost my old one for the millionth time)
Click to expand...
Click to collapse
Either you are flashing the wrong recovery for the phone - or you renamed a zip file instead of extracting the img file first
Or
Put quotation marks around the file path eg "c:/file path" or navigate to where you have fastboot and the twrp image first so all you have to type is
fastboot flash recovery recovery.img
Also make sure adb debugging is enabled in dev options of phone settings
Also if the bootloader is unlocked you should get a bootloader unlocked warning when the device starts unless you have replaced the boot logo with a modified one
If you haven't replaced this & you don't get said warning your device doesn't have an unlocked bootloader

The console is definatly finding the file. this is not the issueadb debugging is enabled. altho i realised i have the insert pattern before startup enabled and i think that might be interfering.
I am not gettIng the bootloader unlocked warning.

I disabled the pattern on bootup.
I unlocked with oem unlock.
i tried to flash from directory
Same issue
Stil no unlocked warning
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools> fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.468s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.493s
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools>
Click to expand...
Click to collapse

DrunkenPanda2000 said:
I disabled the pattern on bootup.
I unlocked with oem unlock.
i tried to flash from directory
Same issue
Stil no unlocked warning
Click to expand...
Click to collapse
Just to check, have you requested and used the unlock key from the Motorola website? https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a

echo92 said:
Just to check, have you requested and used the unlock key from the Motorola website? https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
I have requested one. haven't received it yet.
The website doesn't show if eligable if click that button.
Also they havent send me anything for an houer after requesting.

DrunkenPanda2000 said:
I have requested one. haven't received it yet.
The website doesn't show if eligable if click that button.
Also they havent send me anything for an houer after requesting.
Click to expand...
Click to collapse
Hopefully they'll send you an email with the code in soon. Sometimes the website is a little slow, but regardless it should say if your device is eligible for unlocking. Is your device a carrier bought device or a retail device or bought from Amazon Prime? They do say if your device is bought from Motorola, to wait at least 24 hours before requesting the code.
Check that the unlock string from your device is properly formatted for the website
Ok, so my device should be eligible, but when in enter my unlock string in your tool, I get an error message. What’s wrong?
Please make sure the string you enter in the tool is:
formatted to fit on one line only
has no spaces (you have to remove them manually)
has no carriage returns (these pesky \n)
is of the right length, e.g don’t forget to append the extra 000000… on the last line
USE THE SCRUB TOOL on the UNLOCK PAGE - ABOVE the INPUT BOX
As an example, this is what is returned with the fastboot command
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 99999999999999993332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
And this is what you should enter in the form; it’s a single line, no spaces but with all the trailing zeroes.
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2A 0C39F951A3E5#1F532800020000000000000000000000
Click to expand...
Click to collapse
credit to: https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1
That code in the email should let you unlock the bootloader and let you flash TWRP, no other way to unlock your bootloader (officially). If you don't get the code after a few tries of the website/waiting for the email, you may have to post on the Motorola forums: https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1

Ok so now i unlocked with the code and when i flash i get the following.µ
Model is cedric XT1676 16GB P5
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools> fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.469s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.510s]
finished. total time: 0.985s
Seems to be working now.

DrunkenPanda2000 said:
Ok so now i unlocked with the code and when i flash i get the following.µ
Model is cedric XT1676 16GB P5
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools> fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.469s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.510s]
finished. total time: 0.985s
Click to expand...
Click to collapse
That looks normal - the 'Image not signed or corrupt' message is normal as TWRP has not been cryptographically signed. As you've unlocked your bootloader that message is informational to alert that you're flashing non-Motorola files to your device (which you are).
I'd reboot to recovery after flashing and perform the other steps required (which appear to include disabling dm-verity: https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737 )

When flashing super su i get the error message
-extracting ramdisc
---failure aborting

DrunkenPanda2000 said:
When flashing super su i get the error message
-extracting ramdisc
---failure aborting
Click to expand...
Click to collapse
Flash Magisk v16.0 instead of su zip. It will work.

shad.man92 said:
Flash Magisk v16.0 instead of su zip. It will work.
Click to expand...
Click to collapse
Thx for the advice i need to act before i post sometimes.
I've done this already now i'm facing issues with the magisk nethunter module. this will be discussed in their thread.

Can i close or remove this ?

DrunkenPanda2000 said:
Can i close or remove this ?
Click to expand...
Click to collapse
Yeah sure.

Boot loader unlock
Shooting Star Max said:
Weird, that validation error is usually shown when bootloader isn't actually unlocked. Have you tried unlocking it again? Have you tried with mfastboot?
Click to expand...
Click to collapse
I have tried a same,got a bootloader and tried with fastboot,but i got error 'need to enable OEM in android settings'
.Actualy my mobile stuck with logo,once moto logo appear its gets shutdown,
Looking for your reply.

Can't flash TWRP - remote failure (SOLVED)

Hi guys!
I hope you can help me, since I've looked everywhere but can only find people with similar but not the exact same problem.
I tried flashing TWRP in order to migrate to a custom ROM. I am currently running official 7.1.1.
When I try to flash twrp (tried several versions) the command window shows me this:
c:\adb>fastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (14522 KB)...
OKAY [ 0.049s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.068s
I tried using Moto fastboot as well but with the same result. I'd really appreciate your help. Please note, that I am not a pro like most you guys so I might have follow-up questions

Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Code:
fastboot boot twrp.img
?

Artim_96 said:
Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Code:
fastboot boot twrp.img
?
Click to expand...
Click to collapse
Yes, I am sure that I am using the right image. I tried several, always checked that they were for addison.
I also unlocked the bootloader in developer options - although now that you mention it: in the fastboot screen it still says oem_locked. So maybe that is the problem?
c:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.047s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.054s

Okay, I managed to unlock the bootloader with the unlock key I got from Motorola.
Now when I try to flash it says:
c:\adb>fastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (14522 KB)...
OKAY [ 0.049s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.280s]
finished. total time: 0.330s
Come ooooon

ischariot_pasadelski said:
Are you sure you flashed the right image? And that your bootloader is unlocked?
And what happens if you use
Yes, I am sure that I am using the right image. I tried several, always checked that they were for addison.
I also unlocked the bootloader in developer options - although now that you mention it: in the fastboot screen it still says oem_locked. So maybe that is the problem?
c:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.047s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.054s
Click to expand...
Click to collapse
Oh Jesus... Bootloader unlock is not just the option in Dev settings. Google it, you'll find a website from Motorola that guides you through the process and provides you with everything necessary

Yes, I did that by now as I said in the post before. Sorry, but I'm a beginner
Now it says that the image is not signed or corrupt. IDK what to do anymore.
Booting in TWRP works but when flashing Lineage from SD card I get the error:
recv error on unevent
and
failed to mount data.
I wiped everything using TWRP and I also tried to use another version of TWRP, so a corrupted file can't be the problem.

I figured it out.
I had to restore the file system by only checking the "System" box when wiping with TPWR - just in case anybody else has the same problems.

So a factory data reset solve the problem? Having your first issue with moto e5 cricket and you can't unlock three bootloader

Artim_96 said:
Oh Jesus... Bootloader unlock is not just the option in Dev settings. Google it, you'll find a website from Motorola that guides you through the process and provides you with everything necessary
Click to expand...
Click to collapse
well, i had it unlocked via the settingsbutton and after read this here , via the website where you can get the 20 bits code, but it is the same result with a code that is the same as the adb devices code, just as before! Only thing that is changed is a warning when you starts the phone up.

ischariot_pasadelski said:
Yes, I did that by now as I said in the post before. Sorry, but I'm a beginner
Now it says that the image is not signed or corrupt. IDK what to do anymore.
Booting in TWRP works but when flashing Lineage from SD card I get the error:
recv error on unevent
and
failed to mount data.
I wiped everything using TWRP and I also tried to use another version of TWRP, so a corrupted file can't be the problem.
Click to expand...
Click to collapse
Can you tell me how you got the phone twrped, pls?