Database Users

signature verify fail

I can't boot my phone normally and in recovery mode.
I can boot only in fastboot mode. I don't know why it appens...
The problem is that I can't flash radio, system etc. beacuse I have this error
"signature verify fail"
Is there anything that I can do?
Thank you for helping me...

What radio, hboot version is shown on the fastboot screen and what carrier was the phone originally on (ie carrier brand on the phone, this may or may not be your current mobile carrier)
The signature error is an indication of an s=off spl.. but I need more info to tell you the easiest way to proceed.

I have the samve problem,
I had:
fastboot earse system -w
---------------> ok
fastboot earse recovery
---------------> ok
fastboot flash recovery recovery.img
---------------> failed:
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checki
FAILED (remote: signature verify fail)
Now i only enter to fastboot mode
i think the reason is S-On but i don't know how to change to S-off when i can't enter both system or recovery mode Help me, please!!!!
HBOOT-1.33.0013d
RADIO-2.22.27.08
( sorry if my english is not good ).

i tried : fastboot boot recovery
but it still not work too.
downloading 'boot.img'... OKAY
booting...
Click to expand...
Click to collapse
forever

sunnyboy256 said:
i tried : fastboot boot recovery
but it still not work too.
forever
Click to expand...
Click to collapse
you are on a perfected SPL (1.33.0013d) where you have only a limited number of fastboot commands available. You should look here and read the OP, than you should be able to find a solution for your problem.

Thank you a lot! Sloved!

[Q] Recovery Flash Problem

Hey
I just flashed first with clockword 3.0.0.5 to Swift and then 3.0.2.8
When i flash i get this on CMD
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\android-sdk-windows\adb+fastboot>fastboot.exe flash recovery C:/Recovery.img
< waiting for device >
sending 'recovery' (3778 KB)... OKAY
writing 'recovery'... OKAY
C:\android-sdk-windows\adb+fastboot>fastboot.exe reboot
rebooting...
Click to expand...
Click to collapse
Now when i Press Home+Power it wont give me the recovery just normal boot.
BTW: My fastboot is via volume up + Search button + Power is this okay?

fastboot on the GT540 is CAMERA+POWER BUTTON
are you sure you are in Fastboot mode when you send the comand through adb??
later, in fastboot, when it starts rebooting, as soon as you see the screen turning on, press and hold HOME+POWER

Mitalca said:
fastboot on the GT540 is CAMERA+POWER BUTTON
are you sure you are in Fastboot mode when you send the comand through adb??
later, in fastboot, when it starts rebooting, as soon as you see the screen turning on, press and hold HOME+POWER
Click to expand...
Click to collapse
Well Fastboot aint via Cam+ Power at me. It is Volume up + search button + Power it says Cleary FASTBOOT MODE on screen. Yes i am on fastboot mode on it.
Thats exactly what i did but still

as far as I know, fastboot mode is just a light black screen
what rom are you using??

Well at me it says Fastboot mode
and i am using: http://www.mediafire.com/?y7q20212djy40ap
2.1 Fastboot europe

That's the Europe rom from the FAQ, right?
If that's correct, I can confirm that (at least in mine) the fastboot screen is just a dark empty one
The only mode that I've seen with a description message (beside moded ones like Clockwork) is the Download Mode, wich I think is Volume Down + Power
Maybe yours has Recovery in a different keys combination, just like it does fastboot
What do you want to boot into recovery for??

Mitalca said:
That's the Europe rom from the FAQ, right?
If that's correct, I can confirm that (at least in mine) the fastboot screen is just a dark empty one
The only mode that I've seen with a description message (beside moded ones like Clockwork) is the Download Mode, wich I think is Volume Down + Power
Maybe yours has Recovery in a different keys combination, just like it does fastboot
What do you want to boot into recovery for??
Click to expand...
Click to collapse
To make a recovery and i am reflashing yes from faq
Edit: Didnt work
Edit: Flashed with M5 2.3.4 It worked

Hi!
I want to update recovery from fastboot
2.5.05 => recovery_clockwork_4.0.1.4_swift.img
(win7 64bit) command line:
fastboot flash recovery recovery_clockwork_4.0.1.4_swift.img
windows response:
sending 'recovery' (3792 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
fastboot screen:
suspend
suspend
reset
EP1/out FAIL nfo=40 pg()=15418
portchange
usb_read() transaction failed
fastboot: oops!
reset
portchange
any ideas?
sorry my english
thanx

Try this: Pull out the battery and go back into fastboot. Type:
Code:
fastboot erase recovery
fastboot flash recovery recovery_clockwork_4.0.1.4_swift.img
If that doesn't work, try reinstalling your fastboot drivers (In Device Manager)

thanks, work it

Can not flash anything, PLEASE HELP

ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks

zendick said:
ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks
Click to expand...
Click to collapse
There should be an option on fastboot to go to bootloader and then from there recovery should be available, is that option available to you?

yes but recovery won't boot, sits at mt4g boot screen or sits at 3 skaters in center screen, depending on how I access it (ie go to fastboot then back again)

Power down your phone, hold volume down and the power button. That will take you into the hboot screen. You can then select to go into recovery from there.

thats what I have tried, it goes to three skaters center screen does nothing

I have tried flashing recovery from fastboot
tried hboot from fastboot
tried radio from fastboot
NOTHING flashes trust me I have been androiding for a while now never had I had a problem like this.

zendick said:
thats what I have tried, it goes to three skaters center screen does nothing
Click to expand...
Click to collapse
Is three skaters your boot animation or splash screen? Not sure what that is referring to.

the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens

zendick said:
the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens
Click to expand...
Click to collapse
Oh ok, i know what your talking about now. Your on the bootloader screen under fastboot. And when you select recovery option it does not boot into recovery?

correct and like i said I have tried to reflash everything from fastboot but no go

Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error

got recovery to boot but get
e:can't mount /cache/recovery/command
etc
tried to mount, tried to format
no go

What do you mean tried ruu??
zendick said:
Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error
Click to expand...
Click to collapse
Edit: nvm. Is doing RUU better option than loading PD15IMG.ZIP on sdcard and doing it that way?
Sent from my SGH-T959 using XDA App

tried a pd15 and it doesn't complete, drops a failed message

Sounds like you maybe victim of fail-pu. But if thats not the case and you don't care about your "/data" and just want working phone again then I suggest from fastboot you do "fastboot flash recovery recovery.img" which will replace the current recovery.img and flash it to mmcblk0p21. Once thats done do "fastboot erase system -w" and it will nuke everything so /system, /data, ect will all be erased. After that you can enter recovery by selecting it from hboot and then do factory wipe and flash another rom.
Keep in mind you will run in to errors in recovery after -w as its normal but depending on the fail-pu if you do get the failed partition update flag you can't make any changes as the errors will stick because you can't format the drives. Also the new recovery.img for CWMR can be found in dev section if not post here and ill send you.

I don't care at all about the data (I am well backed up) but I can't flash a recovery I have tried through fastboot, I agree the partition is F_D but I will try the erase system -w and see if that lets me do anything
thanks

uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s

Exactly what I got too, seems we have bricked our phones. Wish I had a way of making the phone unable to boot to recovery or at all.
zendick said:
uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App

I dont get how a phone can run for weeks since its last flash and have this happen, I made no changes updates etc just running as normal.
Is there a way to wipe evidence of cm of so I can get this phone repaired? To me this obviously a faulty emmc, I just can't see it being anything else.
or is it possible to boot recovery on sd like the nook?

any ideas on how to wipe cm bits atleast?

[Q] Bootloop after flashing, TWRP not available..

Hello guys,
Frank is writing. Sorry for disturbing, but i´m in big trouble right now. I made a Factory reset, wipe Dalvik etc. and flashed the PA Aosp Mako 4.0 + latest Gapps.. Nothing special so far, but now my Nexus is still in a bootloop. If i go to the recovery mode, i have no access to TWRP just have the possibility to choose between Start, Start bootloader, Power off, or Recovery Mode. But if i go to the recovery mode the bugdroid is there and nothing happens further. After connecting the device to my mac there is a message on the screen that it´s in download mode?! i didn´t seen this before.. So if you have any solution, it would be great. a factory reset to if possible or even necessary.
Right now I am at my wits end. May someone has an advice for me what to do? i can´t imagine christmas without my beloved smartphone.. ;(
Thanks for your attention!
cheers
Frank

You need fastboot working on your computer, not sure of the exact steps for a mac, but if you download the Android SDK it will be in there. Then you can directly flash a factory image for your phone from the fastboot screen. (The one you describe with start, start bootloader, etc)
You can download the factory images here https://developers.google.com/android/nexus/images#occam
Android sdk for mac http://dl.google.com/android/android-sdk_r22.3-macosx.zip

hey.. thank you for your reply. i downloaded the required files but how to get the access with terminal when it´s still not possible to start the phone? If i type in ./adb devices in terminal just following popped up but nothimg else:
-bash: /Users/frankherrmann/Desktop/adt-bundle-mac-x86_64-20131030: is a directory
do u know what to do now?

At the dead android screen, hold the power button and press vol+. Does it get you to stock recovery?

unfortunately nothing happens the screen turns off, that´s all... ;(

You should try flashing a stock 4.4.2 occam image using fastboot. This would return you to stock and you can then root and install TWRP or CWM.

endxpen tyrants
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image. but anyway, it seems that i can´t get the access to the phone. if i go in the adt folder and use the command adb services in the terminal my device will not be recognized.
Frank-iMac:adt-bundle-mac frankherrmann$ ./adb devices
List of devices attached
Frank-iMac:adt-bundle-mac frankherrmann$
Do i type in something wrong? maybe it´s just a thinking error by myself
thanks againfor your help!

FrankHPunkt said:
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image and put it in the same folder that i named as adroid tools. i got the access to the folder and after type in the command ./fastboot devices my devices has been recognized and the number too. but if i try to flash the stock image it will not work. i typed in ./fastboot flash and the image name but the failure message -bash: ./flash: No such file or directory
so... i suggest that it´s been just a problem that i typed not the correct command, isn´it?
Franks-MacBook-Pro:Android Tools leherman$ ./fastboot flash /Users/leherman/Desktop/android\ tools/image-occam-kot49h.zip
unknown partition '/Users/leherman/Desktop/android tools/image-occam-kot49h.zip'
error: cannot determine image filename for '/Users/leherman/Desktop/android tools/image-occam-kot49h.zip'
Franks-MacBook-Pro:Android Tools leherman$
Click to expand...
Click to collapse

Sorry, I can't help you with flashing on Mac. Do you have access to a PC?

FrankHPunkt said:
FrankHPunkt said:
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image and put it in the same folder that i named as adroid tools. i got the access to the folder and after type in the command ./fastboot devices my devices has been recognized and the number too. but if i try to flash the stock image it will not work. i typed in ./fastboot flash and the image name but the failure message -bash: ./flash: No such file or directory
so... i suggest that it´s been just a problem that i typed not the correct command, isn´it?
Click to expand...
Click to collapse
Yes you got 2 options,run the flash-all script or flash the files manually for example typing fastboot flash recovery recovery.img or fastboot flash radio radio.img, you didn't specified the partition to flash
Click to expand...
Click to collapse

Hey Frederico,
thanks for your reply i did it as you told me and typed this in terminal : as you can see something should work, but it was not possible to flash the image.
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash radio-mako-m9615a-cefwmazm-2.0.1700.98.img radio-mako-m9615a-cefwmazm-2.0.1700.98.img
sending 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img' (45537 KB)...
OKAY [ 1.715s]
writing 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.718s
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash image-occam-kot49h.zip image-occam-kot49h.zip
sending 'image-occam-kot49h.zip' (429746 KB)...
OKAY [ 15.845s]
writing 'image-occam-kot49h.zip'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.848s
do u have an idea whats still not right. Seems to be on the right way!
thank you very much so far!
Federico_96 said:
FrankHPunkt said:
Yes you got 2 options,run the flash-all script or flash the files manually for example typing fastboot flash recovery recovery.img or fastboot flash radio radio.img, you didn't specified the partition to flash
Click to expand...
Click to collapse
Click to expand...
Click to collapse

FrankHPunkt said:
Hey Frederico,
thanks for your reply i did it as you told me and typed this in terminal : as you can see something should work, but it was not possible to flash the image.
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash radio-mako-m9615a-cefwmazm-2.0.1700.98.img radio-mako-m9615a-cefwmazm-2.0.1700.98.img
sending 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img' (45537 KB)...
OKAY [ 1.715s]
writing 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.718s
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash image-occam-kot49h.zip image-occam-kot49h.zip
sending 'image-occam-kot49h.zip' (429746 KB)...
OKAY [ 15.845s]
writing 'image-occam-kot49h.zip'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.848s
do u have an idea whats still not right. Seems to be on the right way!
thank you very much so far!
Click to expand...
Click to collapse
The right command is ./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.98.img, so it is ./fastboot flash <generic name of partition> <exact name of the file> hope this will work, but my suggestion is to run the flash-all script,it will do it authomatically for you, if you want do it manually,here at step D there are all the commands

Thanks a lot, you made may day! the phone is rebooting....
merry christmas!
cheers
Frank

rooted h918 stuck in bootloop. Can't access TWRP!

My main rooted v20 phone got bumped and now is stuck in a bootloop. I can enter fastboot (some commands working) but can't access TWRP recovery using either VOL + UP and USB cable or VOL DOWN + POWER. I believe the phone is on 10j or 10k if I remember correctly. Bootloader and carrier are unlocked.
Is there a way to just reflash TWRP safely and attempt data recovery and ROM installation without factory reset?
My goal is to attempt recovery first. If that is not an option, I would like to flash to 10p so I can start the rooting process using Lafsploit.

DirtyBreakz said:
My main rooted v20 phone got bumped and now is stuck in a bootloop. I can enter fastboot (some commands working) but can't access TWRP recovery using either VOL + UP and USB cable or VOL DOWN + POWER. I believe the phone is on 10j or 10k if I remember correctly. Bootloader and carrier are unlocked.
Is there a way to just reflash TWRP safely and attempt data recovery and ROM installation without factory reset?
My goal is to attempt recovery first. If that is not an option, I would like to flash to 10p so I can start the rooting process using Lafsploit.
Click to expand...
Click to collapse
Sure, to flash twrp in fastboot mode you do this.
Download latest twrp
With the phone off hold vol down plug USB into phone and computer.
type on your computer:
fastboot flash recovery twrp-3.6.2_9-0-h918.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset. How to factory reset the Lgv20

U
Darnrain1 said:
Sure, to flash twrp in fastboot mode you do this.
Download latest twrp
With the phone off hold vol down plug USB into phone and computer.
type on your computer:
fastboot flash recovery twrp-3.6.2_9-0-h918.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset. How to factory reset the Lgv20
Click to expand...
Click to collapse
Unfortunately no joy. I tried fastboot boot and flash commands and even tried renaming the img file. I tried with 3 different versions of twrp. This was the result:
PS C:\Users\User\NexusTools> fastboot boot twrp-3.6.2_9-0-h918.img
Sending 'boot.img' (24948 KB) OKAY [ 0.771s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
PS C:\Users\User\NexusTools> fastboot flash recovery twrp.img
Sending 'recovery' (23512 KB) OKAY [ 0.854s]
Writing 'recovery' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
I've searched the forums and internet for hours and not coming up with anything. Any other ideas?
Just a note when trying to cold boot to twrp using 'UP VOLUME + CONNECT USB' that the screen flashes download mode for a split second and then reboots.

DirtyBreakz said:
U
Unfortunately no joy. I tried fastboot boot and flash commands and even tried renaming the img file. I tried with 3 different versions of twrp. This was the result:
I've searched the forums and internet for hours and not coming up with anything. Any other ideas?
Just a note when trying to cold boot to twrp using 'UP VOLUME + CONNECT USB' that the screen flashes download mode for a split second and then reboots.
Click to expand...
Click to collapse
That's so odd I have never seen this issue before.
You can try flashing the twrp image to the boot partition.
fastboot flash boot twrp.img
fastboot reboot
Should boot rite into twrp then because the twrp image is on the boot partition. Sounds to be like there may be a hardware problem with this phone.

Darnrain1 said:
That's so odd I have never seen this issue before.
You can try flashing the twrp image to the boot partition.
fastboot flash boot twrp.img
fastboot reboot
Should boot rite into twrp then because the twrp image is on the boot partition. Sounds to be like there may be a hardware problem with this phone.
Click to expand...
Click to collapse
Well unfortunately the flash boot command failed also. I'm guessing because it shows the boot partition size is 0. Any possible way around this?
I'm hoping not but I think you might be right about a possible hardware issue...
PS C:\Users\User\NexusTools> fastboot flash boot twrp.img
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 24076288).
Sending 'boot' (23512 KB) OKAY [ 0.817s]
Writing 'boot' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse

DirtyBreakz said:
Well unfortunately the flash boot command failed also. I'm guessing because it shows the boot partition size is 0. Any possible way around this?
Click to expand...
Click to collapse
I think it's a hardware issue with the ram. I cant think of anything else.
Do a search online for the error message.
Writing 'boot' FAILED (remote: 'unknown command')