Database Users

Stuck in recovery loop

Needless to say, im a noob at this.
Now, ive practically scoured the internet for the solution to this problem for the last two days. (only found one thread which there was no answer to)
I cant enter Download mode:
Odin does however detect my phone(Still in recovery mode)
Gets stuck at: <ID:0/004> SetupConnection..
I get this error:
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
-- Movi_check already executed!!...
--movi_checking done!
update media, please wait
E:can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media: Can't mount DBDATA
copy default media content failed.
Tired entering Down load mode trough ADB, Holding Vol. Up, Vol. Down, And Power/Hold
Tried pushing Update.zip using adb, but permission denied
I honestly can not say how it got to this point.

Sounds like a corrupted partition on your device. Easiest fix would be to ODIN back to stock and use check re-partition in ODIN to go truly back to factory. However you stated you can't get into Download Mode. Either try one of the alternative methods (described below), or make/buy a jig that will put you in it 100% of the time.
1) Remove SIM, SDcard, battery.
2) Hold both volume buttons and connect the usb cable.
3) Insert the battery.
Works for me about 95% of the time.

Help Please! Image signature verify fail

To install to clockwork recovery manually I replaced the recovery.img file but when i restarted my phone it says:
Image signature verify fail
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one
you can remove battery for power down.

muz786 said:
To install to clockwork recovery manually I replaced the recovery.img file but when i restarted my phone it says:
Image signature verify fail
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one
you can remove battery for power down.
Click to expand...
Click to collapse
You probably are not rooted. Did you root via superoneclick?
Hmmm. Go into recovery and install a custom rom then flash
Make sure you do not have a stock rom on your phone.

If you flashed B528 (I think) Official ROM, you might have locked bootloader... not sure...

You can flash an unlocked bootloader, it's in the android development forum. I'm not sure if this is the fix though.
http://forum.xda-developers.com/showthread.php?t=1457490

OP, have you got u8800+?
Sent from my U8800

Same here
I have ideos x5 pro and i replaced the img file to this and i have the same prob.
I cant even recovery bot my phone. Always tha same message. Plz help

Please help .. any update for this issue
Kindly help me as i m facing the same problem in my phone ( huawei g510 )
the same message still appearing and i can NOT log into recovery menu or anything else
only tow thing to see
Pink screen instead of the recovery menu
or " Image signature verify fail "
PLZZZZZZZZ HELP
:crying::crying:

Flash rom.
Put the official rom in sd card and use the button combo on your device to flash.
I do not have u8800+, i only have u8860, they are quite similar and i believe this would work

[Q] Huawei C8815 not able to Boot "Image Signature Verify Fail"

I have Huawei C8815, I am facing the following situation
I installed the stock ROM with 3 keys method, than i unlocked the network with networkunlock.bat file.
Later I tried to install one ROM by CWM Recover and I toggled Signature Verification to OFF
When I restarted my phone, It Shows "Image Signature Verify Fail"
1. My phone is not going to Recovery Mode Menu by Vol+ and Power button.
2. My phone is not going to ADB mode by VOL- and Power button.
In both these situations my phone shows "Image Signature verify fail" Install the image with correct signatures.
3.When I try to install the stock ROM by pressing Vol+ and Vol- and Power button, after step 1 in step 2 it says Update failed.
As per my knowledge when network is unlocked the phone will not accept the stock ROM. For Relocking the network we have a tool OFFICIAL FIRMWARE.BAT but for running the bat file the phone must be loaded in ADB mode. My phone is not loading adb drivers in any situation.
It is showing only drivers Android Sooner adb interface.
In this driver environment i cannot do any adb function with my phone.
What to do? I am stuck
I dont know much about JTAG and all. If anything is possible to do with JTAG or any other method, Please guide me in this matter

This is for Motorola Defy and Defy+. You might be in the wrong section, my friend.

Have you worked it out? I flashed OEM partition carelessly with the img from g610c and get exact that you faced. btw, does your networkunlock.bat file work with the simlock ? please share if you don't mind, thanks
pragyavan said:
I have Huawei C8815, I am facing the following situation
I installed the stock ROM with 3 keys method, than i unlocked the network with networkunlock.bat file.
Later I tried to install one ROM by CWM Recover and I toggled Signature Verification to OFF
When I restarted my phone, It Shows "Image Signature Verify Fail"
1. My phone is not going to Recovery Mode Menu by Vol+ and Power button.
2. My phone is not going to ADB mode by VOL- and Power button.
In both these situations my phone shows "Image Signature verify fail" Install the image with correct signatures.
3.When I try to install the stock ROM by pressing Vol+ and Vol- and Power button, after step 1 in step 2 it says Update failed.
As per my knowledge when network is unlocked the phone will not accept the stock ROM. For Relocking the network we have a tool OFFICIAL FIRMWARE.BAT but for running the bat file the phone must be loaded in ADB mode. My phone is not loading adb drivers in any situation.
It is showing only drivers Android Sooner adb interface.
In this driver environment i cannot do any adb function with my phone.
What to do? I am stuck
I dont know much about JTAG and all. If anything is possible to do with JTAG or any other method, Please guide me in this matter
Click to expand...
Click to collapse

nothing happened, i sent back device to China and they sent new one. now working great

Footer is wrong, signature verification failed

Hello,
I made a mistake and flash a bad kernell to my Note 3. After that it boots only to a black screen and after that it reboot to system recovery. Reboot to bootlader doesn"t work.
When I tried to load new official rom using ADB or "update from external storage", it says "Footer is wrong, signature verification failed".
Its Android 5.0 (see screenshot) and the "bad" kernel is N9005XXUEND3. I cant connect ODIN or KIES. Is there any way to repair it? Thanks for any help.

You cannot update from Storage its the wrong format .
Samsung updates KIES or ODIN .

But It's not possible to connect ODIN or Kies and update from external storage is in the menu of my recovery. There is also "update using ADB". But there is a same problem with footer and verification....

Take it to a repair shop .

Did i brick my GT-I9505 ?

Today i wanted to update my phone from cynaogenmod to a recent lineageos. It followed this guide jfltexx/install, but when i tried to "heimdall flash --RECOVERY ...", the blue progress bar on the phone got to ~99% - then heimdall crashed:
Code:
...
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%libusb: error [udev_hotplug_event] ignoring udev action bind
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Because at that point nothing would change anymore, i unplugged the phone and rebooted. Since then the phone won't boot android anymore and reports "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." when booting to recovery mode. Download mode is still accessible, but worthless:
Flashing the original ROM fails with "Complete(Write) operation failed": imgur
Flashing it with a PIT i found on this forum doesn't work either: imgur
Is my phone completely lost? Is there something i can do?

aenderboy said:
Today i wanted to update my phone from cynaogenmod to a recent lineageos. It followed this guide jfltexx/install, but when i tried to "heimdall flash --RECOVERY ...", the blue progress bar on the phone got to ~99% - then heimdall crashed:
Code:
...
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%libusb: error [udev_hotplug_event] ignoring udev action bind
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Because at that point nothing would change anymore, i unplugged the phone and rebooted. Since then the phone won't boot android anymore and reports "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." when booting to recovery mode. Download mode is still accessible, but worthless:
Flashing the original ROM fails with "Complete(Write) operation failed": imgur
Flashing it with a PIT i found on this forum doesn't work either: imgur
Is my phone completely lost? Is there something i can do?
Click to expand...
Click to collapse
Hello,
Please follow my Guides. I recommend you to follow the guide "clean install from scratch" and also use Odin. Everything you need it's on my thread and in my collection.

Issue Resolved
The solution was to use a shorter USB cable. Thank you so much for making me not loose my faith!