Database Users

Secure Booting Error! Cause: Boot certification verify.

Hello there,
I updated my LG P700 to the v20c 4.1.2 JB version. After that, I couldn't find a wayu to root it, but found Framaroot app and succeeded with it. I got a little cocky how easy it was and downloaded ROM Manager. From it, I chose the CWM installation option and the window said it was a success. However, when I clicked to reboot into the recovery, only this little error appeared - "Secure Booting Error! Cause: Boot certification verify." in the left uper corner of the screen. Nothing worked, so I took out the battery and after turning the phone on, I noticed that all the internal memory got factory reseted or something like that and it is just a blank fresh android - all data was lost.
Long story short: flashing recovery from ROM Manager caused the wipe of the memory.
What happened?

[UPDATE] It could be caused by not unlocking the bootloader. I assumed that ROM Manager checks these things or flashes them with the recovery.
If that's the case (pls tell me) then I should unlock the bootloader. Maybe with this - http://forum.xda-developers.com/showthread.php?t=2197429 Does it work with v20c 4.1.2 android on my LG L7?

yes, the bootloader is locked, you need to unlock

Thanks, now I'm at least on to something. Does the method from the link works on v20c 4.1.2. version?
Sent from my LG-P700 using xda app-developers app

Macors said:
Thanks, now I'm at least on to something. Does the method from the link works on v20c 4.1.2. version?
Sent from my LG-P700 using xda app-developers app
Click to expand...
Click to collapse
it doesn`t matter if you have ICS or JB, it must work

I tried unlocking the bootloader with the Flash_Bootloader.bat file, but the error windows flashes only for a split second. I barely caught it and attached the screenshot of it saying "the system cannot find the path specified". What should I do now?
Phone connected in pc software mode, debuggin is on.
[Update] I moved the CWM folder directly to the local disk C and it worked, but didn't reboot the phone. I had to unplug it and then turn on. How to check if my bootloader is unlocked? I don't want any more fails with flashing the recovery ;/

Macors said:
I tried unlocking the bootloader with the Flash_Bootloader.bat file, but the error windows flashes only for a split second. I barely caught it and attached the screenshot of it saying "the system cannot find the path specified". What should I do now?
Phone connected in pc software mode, debuggin is on.
[Update] I moved the CWM folder directly to the local disk C and it worked, but didn't reboot the phone. I had to unplug it and then turn on. How to check if my bootloader is unlocked? I don't want any more fails with flashing the recovery ;/
Click to expand...
Click to collapse
you were needed to write adb reboot to rebbot your phone after, and the only way to chech the bootlaoder is to go on download mode or recovery

Everything is working, just rebooted into Recovery from the rom manager. By the way, how does this adb work? Do I have to run the .exe file after the .bin ?

Macors said:
Everything is working, just rebooted into Recovery from the rom manager. By the way, how does this adb work? Do I have to run the .exe file after the .bin ?
Click to expand...
Click to collapse
start - run cmd - cd %ADB% - and here you are

same here
Im using an lg lucid vs840 and is recently rooted, i downloaded rom manager and cyanogen mod 11, but when i try to install rom from sd card it reboots saying,
boot errer cause boot certification verify
Enter fast reboot...
Enter fast reboot...
Long time no see!
I can still use my phone but i cant install a new rom, any one help?
Thank you for reading.

lol nobody ever answers this same question many times on this site.... sorry first post but I get all my info from hereeeeee for a long time now

My LG LS980 device is now bricked

I need big help, my LG LS980 device is now bricked currently works only in recovery mode with ADB commands, any firmware I tried to upload I did not succeed
adb devices
List of devices attached
03xxxxxxxxxxxx07 sideload
adb sideload aokp_ls980_kitkat_unofficial_2014-01-16. zip
sending 100%
on my screen devices
finding update package
Opening update package
Verifying update package
Installing update
assert failed: run_program ("/system/bin/loki.sh") == 0
Installation aborted.
I've tried other firmware that is supposed to my device with similar result
You may need to restore to stock firmware but I can't figure out the process.
Is there anyone who can help me to restore the device

follow steps to reroot and push loki to device, reinstall recovery. try install again.
before redownload different rom and try to install that, aokp is buggy rom anyway, latest 16th build doesnt boot .

bachera said:
follow steps to reroot and push loki to device, reinstall recovery. try install again.
before redownload different rom and try to install that, aokp is buggy rom anyway, latest 16th build doesnt boot .
Click to expand...
Click to collapse
Thanks for your reply, my problem is that I don't understand how do reroot the device.
The device does not have many options, pressing the buttons (power and Vol +) the device enters in a State Factory Hard Reset.
Pressing (power and Vol-) goes into recovery mode and loads the black screen with anticipation for the adb commands
reboot system now
update from external apply sdcard
apply update from cache
apply update from ADB
wipe data/factory reset
wipe cache partition
With closed then press the device (Vol +) and connect the USB cable enters into Download Mode, here you also don't know what to do.
When I hit the power button just opens the device showing the logo of LG and the led flashing in green/blue and after a while makes itself restarted
I searched the forum for reroot and saw that need to do some settings on the device to do root, did I forget something and so I do not understand?
Sorry, I don't understand and become tedious but it's my first time playing with the object

so, you dont have recovery now?
"adb reboot recovery" not working ?

Based on what you said, you are able to get in recovery and adb is working, then push the ROM zip file over and reflash it in recovery.

I'm happy because I just unbrick my device by selecting Download Mode Firmware Update and with the LGFlashTools loaded LS980ZV8_ software 13.51097. tot.
Now I lie in my original problem, I want to unlock to accept SIM card from another provider and another country.
Some help to be able to start from somewhere the unlock process?

id3210 said:
so, you dont have recovery now?
"adb reboot recovery" not working ?
Click to expand...
Click to collapse
Who not any command except devices-sideload-kill server-start server-reboot
any other command, I was giving "error close"
votinh said:
Based on what you said, you are able to get in recovery and adb is working, then push the ROM zip file over and reflash it in recovery.
Click to expand...
Click to collapse
to command push, I was giving "error close"
But all ok, unbrick my devices with LGFlashTools

Great!
Good to hear that.

I need help as well. My phone ls980 is bricked only works in recovery TWRP. Can someone please help me?

antbox12 said:
I need help as well. My phone ls980 is bricked only works in recovery TWRP. Can someone please help me?
Click to expand...
Click to collapse
Did you accidentally accept that update too?
Sent from my SM-N900P using Tapatalk

natefuhr said:
Did you accidentally accept that update too?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
No but I fixed it. I had to put it in download mode and flash the stock rom back to it.

[Q] Razr M Stuck in Fastboot

Before I start. I would like to address the reason why. The first thing I hated about Motorola is that when you have updated to Jellybean OTA. It won't be unlocked. Unlike my past phones (ex: Samsung)
1) So it started when I installed SAFESTRAP, which did installed successfully.
2) Placed the Eclipse ROM in the root of my sd card.
3) Made a new ROM SLOT.
4) Saving some space, I deleted the whole /stock files. (Factory reset, wipe data and so on.)
5) When I was about to launch it. Everything was smooth until when I tried to delete files. Nothing can't be deleted or transferred. Which is weird.
6) Out of clumsiness, since I loved the JB look and thinking that would fix my file problem, I downloaded the Eclipse ROM ( the one I think isn't safe-strap compatible)
7) When I was about to boot to the system. It got stucked on ap fastboot, recovery can be accessed but even the button combos can't boot it normally.
The error shown :
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
Anyone can help me? Thank you so very much if you did.

Cyb3rw0lfest1 said:
Before I start. I would like to address the reason why. The first thing I hated about Motorola is that when you have updated to Jellybean OTA. It won't be unlocked. Unlike my past phones (ex: Samsung)
1) So it started when I installed SAFESTRAP, which did installed successfully.
2) Placed the Eclipse ROM in the root of my sd card.
3) Made a new ROM SLOT.
4) Saving some space, I deleted the whole /stock files. (Factory reset, wipe data and so on.)
5) When I was about to launch it. Everything was smooth until when I tried to delete files. Nothing can't be deleted or transferred. Which is weird.
6) Out of clumsiness, since I loved the JB look and thinking that would fix my file problem, I downloaded the Eclipse ROM ( the one I think isn't safe-strap compatible)
7) When I was about to boot to the system. It got stucked on ap fastboot, recovery can be accessed but even the button combos can't boot it normally.
The error shown :
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
Anyone can help me? Thank you so very much if you did.
Click to expand...
Click to collapse
Run this from windows
It's Russian . Just say yes. http://forum.xda-developers.com/showthread.php?t=2656659

Flash Failure
aviwdoowks said:
Run this from windows
It's Russian . Just say yes. http://forum.xda-developers.com/showthread.php?t=2656659
Click to expand...
Click to collapse
It now says Fastboot Reason : Flash Failure
I have tried fastboot option like from House of Moto and even the Droid Razr M Utility, but everytime it reaches
sending boot or system. it is stuck at that point.
Using RSD Lite, it shows failed flashing process gptmain0.bin (Something like that.)
I took the gptmain0.bin from the GPT Fix version of Droid Razr M Utility, placed it in there, and it reaches to failed flashing process tz.mbn
What to do? I'm all out of options really. Thanks.
UPDATE: Tried the logo.bat you sent me, it just says waiting for device. It won't even budge a little. Back to the usual hab boot error. Successfully flashed it using it 1.10. Just that I'm back to the first part. (Boot failure)

So you are locked on ...94 (1) right?

Boot Failure
aviwdoowks said:
So you are locked on ...94 (1) right?
Click to expand...
Click to collapse
Tried the logo.bat you sent me, it just says waiting for device. It won't even budge a little. Back to the usual hab boot error. Successfully flashed it using Razr M Utility1.10 (I don't know what version it flashed.). Just that I'm back to the first part. (Boot failure)

aviwdoowks said:
So you are locked on ...94 (1) right?
Click to expand...
Click to collapse
^^^^^^^^^^ what he said.
Build you are on? Locked boot?

aviwdoowks said:
^^^^^^^^^^ what he said.
Build you are on? Locked boot?
Click to expand...
Click to collapse
Now I can access safestrap recovery.
Shows
Unable to mount '/data' (tw_mount)
Unable to mount '/cache' (tw_mount)
Unable to mount '/ss' (tw_mount)
Unable to mount 'datamedia' (tw_mount)
Failed to mount /datamedia (Invalid argument)
Everytime I do something in the safestrap..

Cyb3rw0lfest1 said:
Now I can access safestrap recovery.
Shows FAILED TO MOUNT /DATAMEDIA (INVALID ARGUMENT}
Click to expand...
Click to collapse
Why do think you are on matt's version? If you were you could unlock!
You are on the one you last took the ota for or was on the phone. That is what locked means.
All you can do is rsd restore the above version or upgrade.

aviwdoowks said:
Why do think you are on matt's version? You are on the one you last took the ota for or was on the phone. That is what locked means.
All you can do is rsd restore the above version or upgrade.
Click to expand...
Click to collapse
I can access Safestrap recovery, flashed the boot.img separately. If I used RSD, it will only show failed flashing process gptmain0.bin or the tz.mbn

Cyb3rw0lfest1 said:
I can access Safestrap recovery, flashed the boot.img separately. If I used RSD, it will only show failed flashing process gptmain0.bin or the tz.mbn
Click to expand...
Click to collapse
Your boot is locked!
Read more.
I have a signature link...
Learn how to rsd ..94 & get on my SS dst rom.
Xposed works on locked boots.

aviwdoowks said:
Your boot is locked!
Read more.
I have a signature link...
Learn how to rsd ..94 & get on my SS dst rom.
Xposed works on locked boots.
Click to expand...
Click to collapse
Well now the only thing I can access is Safestrap recovery. Is there anyway I can fastboot in the safestrap recovery. The only thing I can see clearly in my Safestrap is that it can't mount CACHE or /CACHE/RECOVERY
Successfully fixed it myself. All it takes is trial and error all the way and the correct boot.img.

adb sideload "Zip signature verification failed!"

I'm on a Nexus 6p with resurrection remix (for android 6.0.1) trying to flash back to stock 6.0.1. I've been attempting to sideload angler-ota-mtc20l-095e81f7.zip on TWRP (After wiping Dalvik, system, data, and cache) but it keeps saying "Zip signature verification failed!" in my phone and "total xfer: 1.00x" on cmd. I had a backup which I attempted to restore after this failed several times but this left me in a bootloop. Any solution would be appreciated. If you need more information just ask.

Hskom said:
I'm on a Nexus 6p with resurrection remix (for android 6.0.1) trying to flash back to stock 6.0.1. I've been attempting to sideload angler-ota-mtc20l-095e81f7.zip on TWRP (After wiping Dalvik, system, data, and cache) but it keeps saying "Zip signature verification failed!" in my phone and "total xfer: 1.00x" on cmd. I had a backup which I attempted to restore after this failed several times but this left me in a bootloop. Any solution would be appreciated. If you need more information just ask.
Click to expand...
Click to collapse
You'll have to flash the full factory image, not an OTA. You won't be able to side load or flash from recovery. You can either use ADB to flash the full image with the included flash-all.bat, or a toolkit like NRT.

v12xke said:
You'll have to flash the full factory image, not an OTA. You won't be able to side load or flash from recovery. You can either use ADB to flash the full image with the included flash-all.bat, or a toolkit like NRT.
Click to expand...
Click to collapse
I exactly have the same issue but, if I understand correctly, because my device is locked I'm unable to flash the factory image. My phone got bricked during a system update. I had this issue once and I was able to recover it with OTA sideload. But this time it doesn't work: when I do the OTA sideload it gives me the signature verification error.
How could I overcome it?

D4rkFloors said:
I exactly have the same issue but, if I understand correctly, because my device is locked I'm unable to flash the factory image. My phone got bricked during a system update. I had this issue once and I was able to recover it with OTA sideload. But this time it doesn't work: when I do the OTA sideload it gives me the signature verification error.
How could I overcome it?
Click to expand...
Click to collapse
Hi... More infos would help troubleshooting the issue more efficiently.
What was the initial build before the device got bricked?
What was the build "system update" that bricked your phone? Did you update manually or through a pushed OTA? If manually, how did you flash it /bricked your phone?
Finally, which build did you try to Sideload?

5.1 said:
Hi... More infos would help troubleshooting the issue more efficiently.
What was the initial build before the device got bricked?
What was the build "system update" that bricked your phone? Did you update manually or through a pushed OTA? If manually, how did you flash it /bricked your phone?
Finally, which build did you try to Sideload?
Click to expand...
Click to collapse
Thanks for your help.
My current build before the phone got bricked is N4F26I .
I think the update that bricked my phone was N4F26O.
I applied the OTA from the recovery system by selecting "Apply update from ADB" and then doing an adb sideload.
More info:
– I have tried to sideload the OTA images for N4F26I, N4F26J, N4F26O but for all of them I get the error above (I downloaded the OTA image files from Google page)
– Re-downloaded the files, but no joy.
– Phone is not rooted. It had the stock image
- Device shows as LOCKED. If I understand correctly, when device is locked it's not possible to flash the factory image
- USB debugging is enabled
this is the error which happens when I reach 47% of the sideload:
E: failed to verify whole file signature
E: signature verification failed
E: error 21
Installation aborted.

D4rkFloors said:
Thanks for your help.
My current build before the phone got bricked is N4F26I .
I think the update that bricked my phone was N4F26O.
I applied the OTA from the recovery system by selecting "Apply update from ADB" and then doing an adb sideload.
More info:
– I have tried to sideload the OTA images for N4F26I, N4F26J, N4F26O but for all of them I get the error above (I downloaded the OTA image files from Google page)
– Re-downloaded the files, but no joy.
– Phone is not rooted. It had the stock image
- Device shows as LOCKED. If I understand correctly, when device is locked it's not possible to flash the factory image
- USB debugging is enabled
this is the error which happens when I reach 47% of the sideload:
E: failed to verify whole file signature
E: signature verification failed
E: error 21
Installation aborted.
Click to expand...
Click to collapse
Did anyone ever figure out this situation. I'm in exactly same situation. Can't sideload full ota image, quits in middle with signature verification. Bootloader is locked and device wont boot up to enable oem unlocking.

How to get past
adb sideload "Zip signature verification failed!"​Disable signature verification

xinulhacker said:
Come superare
adb sideload "Verifica firma zip fallita!"​Disabilita la verifica della firma
Click to expand...
Click to collapse
How?

FUBAR - Bricked - Cannot enter Fastboot - Only Stock TWRP

Hello, I am in bad shape, this never happened to me before,
I own a A2017G and I tried to go to Nugart. But every thing went south and FUBAR.
I do not know how to fix it. The problem is that I cannot do a adb reboot edl and option 2 pushing +- does not get me into EDL either.
Therefore I cannot instal TWRP and I have the stock and I get the linux pinguin.
1. I tried to upload into the sd card a update.zip with a stock 09 but the Stock TWRP tells me that I cannot install from SDcard
2. I go to install through ADB , and that gets me into sideload.... however every file I try to update which is large 2.5gig fails and the small ones (recovery.img in a zip) tells mes that I have the wrong header.
What can I do?
Is there a way of sideload twrp???
Thanks for any support!!!

The error I get when uploading a Zip through TWRP from ADB:
Finding update package...
Opening update package....
Verifingy update package....
E: footer is wrong
Update package verification took 0.0 s (result 1)
E: Signature verification failed
Instalation Aborted

https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552

marcus.linkenbach said:
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
Click to expand...
Click to collapse
I new te risks.. I am willing to brick... Done it 1000 of times in my first xperia x10, xperia Z2 and ZTE axon 7...just the first time I do not know if to fix it...
If I just get into edl.... No pain no gain

Let me know if it worked for you.

marcus.linkenbach said:
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
Click to expand...
Click to collapse
Like always there is away, knowledge is the power to do things that others cannot

j77moduss said:
Like always there is away, knowledge is the power to do things that others cannot
Click to expand...
Click to collapse
The magic words... Usb modified cable.. Deep flash cable...
This will allow me to get into Edl and re flash TWRP and flash a zip and be safe...
Knowledge is blitz!!!