Develop Bugs

Secure Booting Error! Cause: boot certification verify

Hello all,
LG Optimus G Pro user here (LG-F240S). I recently rooted my phone, then used Gomdol's tool, which roots the phone and installs CWM recovery at the same time. I had initially thought that the application also unlocks the bootloader, but since then found out it doesn't.
Anyways, the first time rebooted into recovery, I flashed a ROM (specifically for F240S), which wasn't successful for some reason. Now, when I boot up the phone, it keeps saying "Secure Booting Error! Cause: boot certification verify"
I have tried everything, from the Volume down + Power + Home to erase everything and do the factory reset, but it doesn't work. I have also downloaded the stock firmware, and tried the KDZ_FW_UPD application to flash the stock firmware, which also did not work (Extract File Error). My last resort was using LGMobile Support Tool, but it keeps telling me to recharge my battery (my batter is currently recharged to 100%, and the USB is plugged in, so something is very wrong here).
I would really appreciate any help, It's been 3 days now without being able to use my phone and it sucks
Thanks!
J

Might wanna try this
ca12bon said:
Hello all,
LG Optimus G Pro user here (LG-F240S). I recently rooted my phone, then used Gomdol's tool, which roots the phone and installs CWM recovery at the same time. I had initially thought that the application also unlocks the bootloader, but since then found out it doesn't.
Anyways, the first time rebooted into recovery, I flashed a ROM (specifically for F240S), which wasn't successful for some reason. Now, when I boot up the phone, it keeps saying "Secure Booting Error! Cause: boot certification verify"
I have tried everything, from the Volume down + Power + Home to erase everything and do the factory reset, but it doesn't work. I have also downloaded the stock firmware, and tried the KDZ_FW_UPD application to flash the stock firmware, which also did not work (Extract File Error). My last resort was using LGMobile Support Tool, but it keeps telling me to recharge my battery (my batter is currently recharged to 100%, and the USB is plugged in, so something is very wrong here).
I would really appreciate any help, It's been 3 days now without being able to use my phone and it sucks
Thanks!
J
Click to expand...
Click to collapse
Hey mine did this i used the instruction in the thread below but i had the e980 so you might have to get your stock files but worth a try?
http://forum.xda-developers.com/showthread.php?t=2302660

Simply follow this method
http://forum.xda-developers.com/showthread.php?t=2396048

Hey man, I'm in the same boat, but I have the E988. What did you end up doing?

any idea?????
tase25 said:
Hey man, I'm in the same boat, but I have the E988. What did you end up doing?
Click to expand...
Click to collapse
i have the same problem here!! E975 when i dot the classic staff for custom rom i go to recovery i i see this in to my phone....boot certification verify
stock rom 4.4.2kk....what i mast do guys plz help

ca12bon said:
Hello all,
LG Optimus G Pro user here (LG-F240S). I recently rooted my phone, then used Gomdol's tool, which roots the phone and installs CWM recovery at the same time. I had initially thought that the application also unlocks the bootloader, but since then found out it doesn't.
Anyways, the first time rebooted into recovery, I flashed a ROM (specifically for F240S), which wasn't successful for some reason. Now, when I boot up the phone, it keeps saying "Secure Booting Error! Cause: boot certification verify"
I have tried everything, from the Volume down + Power + Home to erase everything and do the factory reset, but it doesn't work. I have also downloaded the stock firmware, and tried the KDZ_FW_UPD application to flash the stock firmware, which also did not work (Extract File Error). My last resort was using LGMobile Support Tool, but it keeps telling me to recharge my battery (my batter is currently recharged to 100%, and the USB is plugged in, so something is very wrong here).
F240S user here bro. I feel you
I would really appreciate any help, It's been 3 days now without being able to use my phone and it sucks
Thanks!
J
Click to expand...
Click to collapse
on your boot certification problem, I had that same problem before and made me panic for two days. I tried LG mobile support tool and worked for the first time. few weeks ago, I also encountered the same error on LG Mobile support tool (battery error,right?) I used I also used the KDZ_FW_UPD application and yes, extract error. but you know what the magical thing is? I found the G2 KDZ flasher from the G2 thread..
even if this was from G2 thread, it worked for my device.
here is the link and of course thanks to @hyelton for bringing this wonderful fix. now, I don't have to worry about bricking my phone again(except for hard bricking, of course).
http://forum.xda-developers.com/showthread.php?t=2432476
one more thing: make sure you download the KDZ. there is a thread here that links to that. but I think you have the right kdz now so just follow the steps. make sure you are in download mode press volume up and down (only the volume up and down. not the home or power) and then plug the cord.

guys, this happens when installing custom rom with lg stock rom in it and your device is not fully unlock. to lessen the hassle of worrying trying to reflash to the stock rom and downloading those huge files..just download any custom pure android rom , slimkat, cm11, etc then flash to your recovery..it would boot again without that error on boot certification. only that your on pure android rom but that's ok

nuvkyl20 said:
guys, this happens when installing custom rom with lg stock rom in it and your device is not fully unlock. to lessen the hassle of worrying trying to reflash to the stock rom and downloading those huge files..just download any custom pure android rom , slimkat, cm11, etc then flash to your recovery..it would boot again without that error on boot certification. only that your on pure android rom but that's ok
Click to expand...
Click to collapse
How do i flash the rom when i cant get into recovery? I have the same issue om my rooted g pad whit stockrom. I want to flash cyagenmod.

HELP PLEASE! My Lg G Pro e988 stays forever on this "Secure booting error! Cause: boot certification verify! Can't get in download mode. I have tryed all sort of combination keys but everytime this error pops up. My phone was on stock rom, then an official update started to download and ask me to reboot. After reboot this error!
HELP!

You should be able to get in download mode by following these steps. First take out the battery for atleast 5seconds, put it back in, then press and hold both vol + and vol - and within 2seconds plug in the usb cable, your computer should make the sound of a new device connected, when you hear that let go of the volume keys. The screen should say download mode now.
Sent from my LG-E980 using XDA Free mobile app

ivoh95 said:
You should be able to get in download mode by following these steps. First take out the battery for atleast 5seconds, put it back in, then press and hold both vol + and vol - and within 2seconds plug in the usb cable, your computer should make the sound of a new device connected, when you hear that let go of the volume keys. The screen should say download mode now.
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't work! I did exactly what you say. No sound on pc, just that error on phone screen and no download mode
What should I do?
Thanks

Try booting into recovery, hold power and vol -. Or try power and vol +
Sent from my LG-E980 using XDA Free mobile app

ivoh95 said:
Try booting into recovery, hold power and vol -. Or try power and vol +
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
I have sent it to warranty and they told me that the phone was rooted, they sent me a picture with the back of the phone showing the imei and serial number and a front picture showing me that the phone has the app SuperSu.
They told me that the phone need a new motherboard that cost ~340 $.
Why do they need a new motherboard ? because the phone was not hard bricked.
I will get my device back.
Is possible to get it back with some modifications? I mean if they managed to boot it and see the SuperSu app.
I know to work with LG Flash Tool, so all I need is to put it to download mode.
All the above key combination didn't work. Power and vol- or power and vol+ ......
I will contact you again when i'll have my device.
Thanks!

yackmaan said:
I have sent it to warranty and they told me that the phone was rooted, they sent me a picture with the back of the phone showing the imei and serial number and a front picture showing me that the phone has the app SuperSu.
They told me that the phone need a new motherboard that cost ~340 $.
Why do they need a new motherboard ? because the phone was not hard bricked.
I will get my device back.
Is possible to get it back with some modifications? I mean if they managed to boot it and see the SuperSu app.
I know to work with LG Flash Tool, so all I need is to put it to download mode.
All the above key combination didn't work. Power and vol- or power and vol+ ......
I will contact you again when i'll have my device.
Thanks!
Click to expand...
Click to collapse
Any updates?

Long story with guys at warranty. I asked them to prove that the phone in those pictures is mine. From the picture showing my imei, yes is mine. But from the picture showing supersu app....they don't convince me. Every phone could have installed supersu app without being rooted. So i asked them to provide me another picture that will show the google account that was registered on phone and another with all my apps installed. They didn't send me such photos.
If they managed to revive my device and showing me there is a supersu app, that means they don't need to change the motherboard.
Am i right?
So i get my phone back working and they cut my warranty.
I tried vol+ and vol- and usb cable and download mode appeared.
Thankd!

yackmaan said:
Long story with guys at warranty. I asked them to prove that the phone in those pictures is mine. From the picture showing my imei, yes is mine. But from the picture showing supersu app....they don't convince me. Every phone could have installed supersu app without being rooted. So i asked them to provide me another picture that will show the google account that was registered on phone and another with all my apps installed. They didn't send me such photos.
If they managed to revive my device and showing me there is a supersu app, that means they don't need to change the motherboard.
Am i right?
So i get my phone back working and they cut my warranty.
I tried vol+ and vol- and usb cable and download mode appeared.
Thankd!
Click to expand...
Click to collapse
I smell something weird about LG. They probably put SuperSU on there or they got the wrong phone. Anyway i'm sure the community will help Don't lose faith/hope yet

About the warranty, its very complicated.
The store from which the phone was buyed, took it and send it to another warranty dealer authorized by LG, i guess, which was not named LG.
At last, I sold the phone, i own an lg g2 now and recently flash official lollipop.

Gladly and after some fails and always getting the secure boot certification error, i managed to access the download mode and with LG Flash Tool installed the stock .kdz on my LG L90 D405n.. thx for all the hints..

Before of this secure boot my e988 was working but no download mode. I've encountered this on a LG G2, so after some search i've found out that I must downgrade the bootloader. So, I rooted my device and installed autorec.apk from here http://forum.xda-developers.com/showthread.php?t=2715496 that fixes the " no download mode " .
I don't know how to skip the secure boot error. If someone managed please share with us!

Boot : Error Certification Verify
Hi. I am new to this thread although i had used this thread many times with issues i have had. There is this one issue im having that i can't seem to figure out which im usually good at doing by following forums or threads.
A couple weeks ago i had rooted my LG G Pad 7.0 V410 LTE tablet from AT&T. I had TWRP downloaded into it and i had flashed Candy5 it worked perfectly i just didn't like how it looked so i tryed to flash it back to original stock OS. But now when i boot my tablet up it goes to the LG screen and at the top left it says Boot : Error Certification Error. This has me dumbfounded on what i should do. when i connect the tablet to the computer nothing pops up no tablet connects to the computer. I tryed downloading the drivers and everything but nothing seemed to work. I need help with this issue please!!
I didn't know where else to post this issue due to being new!!!

[Q] Fastboot mode started udc_start() BRICKED!

my LG G PAD v500 is stuck at :
Fastboot mode started
udc_start()
the only thing hat i can do is to be turned off....help!!!!!!!!!!!!!!
:crying:
im unable to go to download mode...... can you please instruct me in detailed in what to do?

Hey i have the same problem
I have the same problem after i did a factory software upgrade and i was rooted but no recovery. did yo ever get it fixed

Solematrix said:
I have the same problem after i did a factory software upgrade and i was rooted but no recovery. did yo ever get it fixed
Click to expand...
Click to collapse
If this error shows up because of bad recovery, boot into normal ROM, root and flash stock recovery or twrp
If this error shows up because of bad boot.IMG, then you'll have to restore firmware from kdz file via download mode.(download mode = plug in usb plus volume up(?)... You should see a "Download" logo, brightness mat be very low and you have to squint )

Thanks
Yes thanx i figured it out from reading threw the forums but your help was much appreciated now to find out why my vk810 will not upgrade to 4.4.2 keep getting a error message
paperWastage said:
If this error shows up because of bad recovery, boot into normal ROM, root and flash stock recovery or twrp
If this error shows up because of bad boot.IMG, then you'll have to restore firmware from kdz file via download mode.(download mode = plug in usb plus volume up(?)... You should see a "Download" logo, brightness mat be very low and you have to squint )
Click to expand...
Click to collapse

Solematrix said:
Yes thanx i figured it out from reading threw the forums but your help was much appreciated now to find out why my vk810 will not upgrade to 4.4.2 keep getting a error message
Click to expand...
Click to collapse
I went to the Verizon store just now, their vk810 were still on 4.4.2, "check for update" says no update
Try updating via WiFi. If you removed any system apps, you need to put them back
Also, at least post the error :/... How can I help you debug if you don't tell me which step had the problem (can't search for update, update failed with x error code, tablet blew up to pieces during update...)

i did post it in another thread i started but never really got answers
paperWastage said:
I went to the Verizon store just now, their vk810 were still on 4.4.2, "check for update" says no update
Try updating via WiFi. If you removed any system apps, you need to put them back
Also, at least post the error :/... How can I help you debug if you don't tell me which step had the problem (can't search for update, update failed with x error code, tablet blew up to pieces during update...)
Click to expand...
Click to collapse
---------- Post added at 10:40 PM ---------- Previous post was at 10:37 PM ----------
i wiped it clean and started from new and it still say the same thing i tried it on wifi same time. i even took out my t mobile sim thinking it was that
paperWastage said:
I went to the Verizon store just now, their vk810 were still on 4.4.2, "check for update" says no update
Try updating via WiFi. If you removed any system apps, you need to put them back
Also, at least post the error :/... How can I help you debug if you don't tell me which step had the problem (can't search for update, update failed with x error code, tablet blew up to pieces during update...)
Click to expand...
Click to collapse

Hi,
Just to know if this problem is solved...
If it is, then this is most probably useless... unless somebody else stumps into the same problem.
If I can guess it correctly, this message typically display when you have rooted your V500, installed a custom recovery from an app flasher (i.e. Flashify, ROMToolBox...) and the recovery isn't compatible with your device and you tried a hard reset.
This means that you are able to boot into fastboot and that is what's going to save you
Why ? Simply put : because you can flash some files using the fastboot command line
Try to flash bootloaders, aboot, boot and recovery just for a try. You can find those I guess.
Regards.

Stuck with "Fastboot mode started"
I was currently on Altev vk81035b-rooted-SU installed but no custom recovery. I followed Altev-Hnk1 instructions for flashing aboot.4.2.2 & commands (dd if=/......Etc) you know the rest) which successfully copied the file. Then when I typed "reboot recovery" BAM, that's when my gPad slapped me in the face with the following--> Fastboot mode started udc_start()
I press & constantly hold "power & down" buttons which always brings me to "System Recovery" screen listing 4 options, "Continue reboot"-"Factory data reset"-"Wipe Cache"-"Safe mode boot". Anytime I have a problem I'll choose "safemode" which always got me back in after any "Boot Verification Errors", but now it doesn't & I'm stuck no matter what I chose. I'm starting to think I may need to connect my laptop and flash the KDZ starting from scratch with plain-Jane Verizon stock!?!? Whatcha think, yes-no-maybe so!?!? LOL

[Q] Please help, stuck im ''Fasboot mode started''

Guys, I'm completely lost.
I rooted my phone, and tryed to use TWRP recovery.
Installed Android Studio Setup Wizzard, openned command window and typed ''adb shell'', ''su''...
But when I tried entering recovery mode to go into TWRP, my phone just got Stuck.
It says: ''Fastboot mode started''
''reset''
''portchange''
''reset''
''portchange''
then i decided to remove the usb cable from the phone and it said more things, now it says ''Fastboot: processing commands''
Even tried to remove the battery but nothing works.
I am a noob when it comes to Roms and flashing this and that, and I know i made a mistake by doing this. Could you guys send me a solution for this? Just want my phone back.
I'm using the LG G3 D855.

If it doesnt start normally into Android OS your phones a goner
Take it into your local service center and tell them the problem occurred while you were trying to apply the Lollipop OTA

[REQ] Help: bootloop after 7.1.1 beta OTA and cannot enter recovery mode

I've been watching several threads for the last few days, and have not seen this exact issue. I would greatly appreciate some help.
Device:
- Nexus 5X LGH790 32GB
- Stock bootloader / fastboot
- Never unlocked / rooted / etc.
The only advanced thing I've done is join the beta program a few months ago to get 7.0 early. Got that without any issue.
Issue:
I received the 7.1.1 OTA on the day it came out. Installed with no problems. The next day, the phone just froze in the middle of regular use. After about 15 seconds, it started boot looping to the Google splash screen. I can hold volume-down to enter fastboot, but when I select recovery mode, it just starts looping again. Pretty much all I could do was power it off. I did find out by accident that if I left it looping for long enough, sometimes it actually loaded normally (I even saw beta program warning/notice). But when I tried using it for more than a minute, it would freeze, reboot, and loop again.
What I've already tried:
- I tried using the WugFresh NRT fix softbrick method. I was able to quickly turn on debugging one of the times that I left it to loop. But when NRT sent a reboot the phone, it threw it back into the loop and NRT stopped recognizing the device.
- I tried to follow the unbrick procedure using a TOT file in this thread: http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766 But even after using LGUP, I still cannot even get into recovery mode.
- I filed a bug in the AOSP here: https://code.google.com/p/android/issues/detail?id=225802.
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.

Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?

DC_Knight said:
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
Click to expand...
Click to collapse
Try fastboot/bootloader mode and fastboot flash the OTA manually.

Update 2: Seems like all the other things I tried over the last few days have caused various unofficial USB drivers to be installed. I've tried uninstalling most of them. I downloaded the google USB driver from latest SDK. But my 5X is still recognized as a Kedacom device when it is sitting at FastBoot.
However, I must have made some progress because I was able to start the sideload process. Unfortunately, I am now stuck on yet another error. The phone hangs at "verifying update package" and then after about 2 minutes... it reboots itself and starts looping again!
I thought I had it. So close. Now I want to throw the phone. Going to sleep, but would be grateful for any other suggestions in the morning.
- DCK

use nrt to erase all partitions, then download 7.1 factory image, unzip and flash one by one the partitions.

DC_Knight said:
...
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Click to expand...
Click to collapse
Sounds like the boot loop issue many people have been having (the hardware/solder issue). It happened to me a few weeks ago after upgrading to Android 7.0. I got a replacement device from google.

If you're bootloader is locked, NRT or any other method to flash the factory image is not going to work. The only suggestion I have is to un-enroll in the beta program and hope your device will boot long enough to flash the ota Google will send the device to get back to 7.0. Note, this will wipe your device.
Sent from my Nexus 9 using XDA-Developers mobile app

Same problem here. It can't be recognized after I reboot to fastboot. So I can't flash anything.

If the device isn't recognized try this http://forum.xda-developers.com/showpost.php?p=69273414&postcount=33. It's worked for a few of us with the same problem
Sent from my Nexus 9 using XDA-Developers mobile app

Enter stock recovery then flash the full ota via adb sideload

Interrupted flashing during "VolumeUp + Power" mode

I have updated my Nexus 5x to 7.1.1 beta and after a day it powered off and I got the infamous red led during charging. I was not able to turn the phone on even after leaving the charger on for some days. I thought it is bricked and left it alone connected to my computer.
However today, out of nowhere Google logo popped up. It was bootlooping, but I was able to enter bootloader and original recovery. I wanted to flash it from bootloader, but was unable, because it was still oem locked. And I was not able to oem unlock, because I did not do the required part in the Developer Tools menu. I tried to adb sideload OTA in the original recovery, but sideloading stopped after uploading ~48% every time.
So I opted for the "VolumeUp + Power" mode flashing. Phone was recognized and I started flashing the appropriate TOT file. However at 33% on phone and 28% on the PC, progress stopped. And after a minute or so phone turned off. Currently it has no signs of life at all. Have I completely bricked it now? Is there a way to recover from interrupted "VolumeUp + Power" flashing mode?
EDIT: at first I though maybe the battery died during flashing. But interruption was not abrupt. First the progress slowed down to halt. And then after some time phone turned off.

It seems not all is lost. Have a blinking red light again after leaving it connected to computer for a day. Back to square one, but at least it is alive.

Your motherboard is dead.
And it is not your fault, mine also died while using beta 7.1 and I sent it RMA. They replaced for a new one.
But in my case i had unlocked bootloader, I flashed back 7.0 and it gave no results, still bootloop that's why I sent

Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Anyway, I tried to RMA it and after giving my IMEI to the Google rep, they said that they could not find it in their system after checking US and UK store records. Also tried calling LG warranty, but they do not know of my IMEI either. I got this phone from Swappa, so I left wondering where did the original owner of this phone got it from. He claimed that he got it as a present...

BlinK_ said:
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Click to expand...
Click to collapse
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.

anazhd said:
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
Click to expand...
Click to collapse
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?

BlinK_ said:
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
Click to expand...
Click to collapse
For now, no way that I can think of. You could try to oem unlock it until it work, just cross your finger I guess?

I have some progress here. Since I was able to sideload various OTA images, I started doing that one by one and seeing if some of them would not bootloop. And after flashing 7.0.0 (NRD91N) from here (https://developers.google.com/android/ota) phone booted successfully and now is working. Will report if I get any problems.