Develop Bugs

[Q] LG G Pad 8.3 secure booting error cause boot certification verify

Hi,
I want to flash my device to Android 4.4.4 Stock Android(Who likes this annoying LG Bloatware?).
When i wanted to get into Recovery Mode using TWRP the LG Logo pops up and in the top-right corner stands:
"secure booting error cause boot certification verify".
I tried everything i know to get into recovery mode, but nothing helped.

Go through the "first time" recovery manual installation procedure found in the CWM thread for the v500. I'm assuming you have a v500.

I have this problem too. Lg gpad 8.3 vk 810

bobdieeule said:
Hi,
I want to flash my device to Android 4.4.4 Stock Android(Who likes this annoying LG Bloatware?).
When i wanted to get into Recovery Mode using TWRP the LG Logo pops up and in the top-right corner stands:
"secure booting error cause boot certification verify".
I tried everything i know to get into recovery mode, but nothing helped.
Click to expand...
Click to collapse
Try This Install This In Ur Pad Press Flash Recovery And Boot it
Hope It Help!
https://app.box.com/s/fqyajojp6wr1i4hu6wqi
(Sorry for my wrong gammar im from philippines)

Jansxel said:
Try This Install This In Ur Pad Press Flash Recovery And Boot it
Hope It Help!
https://app.box.com/s/fqyajojp6wr1i4hu6wqi
(Sorry for my wrong gammar im from philippines)
Click to expand...
Click to collapse
Thanks a million, after hours trying every single method I found across the Web, this was the only thing that managed to get TWRP 2.8 on my v50020d 4.4.2.
It would be interesting though for us to let us know what exactly is that, because I found many people with the same problem than me, and this appears to be the only solution

Maxxd01 said:
Thanks a million, after hours trying every single method I found across the Web, this was the only thing that managed to get TWRP 2.8 on my v50020d 4.4.2.
It would be interesting though for us to let us know what exactly is that, because I found many people with the same problem than me, and this appears to be the only solution
Click to expand...
Click to collapse
Did It Bypass Ur Bootloader?

Jansxel said:
Did It Bypass Ur Bootloader?
Click to expand...
Click to collapse
Well, my problem it was I was using this method (the only one which do not gave me any explicit error) to install TWRP, and when rebooting to recovery it was always loading the stock recovery. That app solved me that instantaneously.
I was a little scared to see first the message "secure booting error, device unlock, so boot success" but it did loaded after TWRP. I guess that is supposed to be that way.

Yep @Maxxd01 That "secure booting error, device unlock, so boot success" it means it bypass ur bootloader to boot into custom recovery

Jansxel said:
Yep @Maxxd01 That "secure booting error, device unlock, so boot success" it means it bypass ur bootloader to boot into custom recovery
Click to expand...
Click to collapse
Good to know

Nexus 7 2013 not going past boot animation

My Nexus 7 2013 running stock 4.4.4 is not able to boot up to the lock/home screen. It just stays at the four dots or petals boot animation indefinitely. It does not freeze(animation goes on smoothly) nor does it go back to the bootloader again.
I have done cache wipe and factory reset.
I have flashed stock 4.4.4 factory image again and in the process unlocked the bootloader as of now.
But there is no change in the situation. I love this tablet and I am desperate to get this sorted out. Please help me.

I am in the same situation. I got my device back from Asus repair today, it was unlocked and running a custom KitKat rom, but only the screen was broken and that was what was repaired (at my own expense).
I turned it on and it was stuck at the 4 swirling dots for more than 20 mins, so I wiped the device completely in TWRP and tried to flash a stock factory image (Lollipop) - same problem. I tried flashing a factory KitKat image, also stuck at boot animation.
I then re-flashed TWRP since it had been replaced by the stock recovery, and then sideloaded a custom Lollipop rom (Screwd) - still same problem.
It is strange that I can use adb and fastboot, but nothing gets past the swirling dots. Hopefully someone can point us both in the right direction....

ems328i said:
I am in the same situation. I got my device back from Asus repair today, it was unlocked and running a custom KitKat rom, but only the screen was broken and that was what was repaired (at my own expense).
I turned it on and it was stuck at the 4 swirling dots for more than 20 mins, so I wiped the device completely in TWRP and tried to flash a stock factory image (Lollipop) - same problem. I tried flashing a factory KitKat image, also stuck at boot animation.
I then re-flashed TWRP since it had been replaced by the stock recovery, and then sideloaded a custom Lollipop rom (Screwd) - still same problem.
It is strange that I can use adb and fastboot, but nothing gets past the swirling dots. Hopefully someone can point us both in the right direction....
Click to expand...
Click to collapse
Ya I can understand. All we can do is wait for useful suggestions.

bump

Clonazepam said:
bump
Click to expand...
Click to collapse
If the tab gets to the spinning dots, it means the bootloader is not corrupt, so there must be a way to restore. Since there's nothing else you can do, why don't you back up the tab, then erase everything, especially formatting the internal storage (using the format button in TWRP) twice, and re-flash a rom. It seems some residue is preventing the thing from booting up. It happened to me on the TF300 a few times when the new bootloader was incompatible with the old one. Good luck.

graphdarnell said:
If the tab gets to the spinning dots, it means the bootloader is not corrupt, so there must be a way to restore. Since there's nothing else you can do, why don't you back up the tab, then erase everything, especially formatting the internal storage (using the format button in TWRP) twice, and re-flash a rom. It seems some residue is preventing the thing from booting up. It happened to me on the TF300 a few times when the new bootloader was incompatible with the old one. Good luck.
Click to expand...
Click to collapse
I tried that but I had no luck. Any other suggestions?

Clonazepam said:
I tried that but I had no luck. Any other suggestions?
Click to expand...
Click to collapse
Depending on the TWRP version, some claim it would fail to format completely. Phil's Touch (Arter's version 6.58.9) however would. You might want to try that. I personally haven't experienced it with this model, so I just pass the information along. Unless the EMMC physical structure is damaged somehow and cannot be written to, in which case the only solution is a replacement motherboard since you cannot find an OEM Emmc, let alone replace and program it.

ems328i said:
I am in the same situation. I got my device back from Asus repair today, it was unlocked and running a custom KitKat rom, but only the screen was broken and that was what was repaired (at my own expense).
I turned it on and it was stuck at the 4 swirling dots for more than 20 mins, so I wiped the device completely in TWRP and tried to flash a stock factory image (Lollipop) - same problem. I tried flashing a factory KitKat image, also stuck at boot animation.
I then re-flashed TWRP since it had been replaced by the stock recovery, and then sideloaded a custom Lollipop rom (Screwd) - still same problem.
It is strange that I can use adb and fastboot, but nothing gets past the swirling dots. Hopefully someone can point us both in the right direction....
Click to expand...
Click to collapse
So you sent your tablet to ASUS to have the screen replaced and they sent it back to you unable to boot? That's not something you should have to deal with, I'd call ASUS and demand that they repair it.

graphdarnell said:
Depending on the TWRP version, some claim it would fail to format completely. Phil's Touch (Arter's version 6.58.9) however would. You might want to try that. I personally haven't experienced it with this model, so I just pass the information along. Unless the EMMC physical structure is damaged somehow and cannot be written to, in which case the only solution is a replacement motherboard since you cannot find an OEM Emmc, let alone replace and program it.
Click to expand...
Click to collapse
I just tried with Philz recovery but still had no luck. i formatted everything and then flashed a factory image but still it's the same.

_MetalHead_ said:
So you sent your tablet to ASUS to have the screen replaced and they sent it back to you unable to boot? That's not something you should have to deal with, I'd call ASUS and demand that they repair it.
Click to expand...
Click to collapse
That's what I've done now, but I was hoping to avoid sending it off for 2-3 weeks after already not having it for the last 2 1/2 weeks

ems328i said:
That's what I've done now, but I was hoping to avoid sending it off for 2-3 weeks after already not having it for the last 2 1/2 weeks
Click to expand...
Click to collapse
Yeah, that sucks. I'd probably try and fix it myself too. But with what ASUS charges for repair you'd think they'd send it back to you on perfect working order. I called yesterday to see what it cost to replace the screen because mine is all scratched up and they wanted $200. Ridiculous. Might as well just buy a new one.

Any other methods to fix this problem anyone?

Clonazepam said:
My Nexus 7 2013 running stock 4.4.4 is not able to boot up to the lock/home screen. It just stays at the four dots or petals boot animation indefinitely. It does not freeze(animation goes on smoothly) nor does it go back to the bootloader again.
I have done cache wipe and factory reset.
I have flashed stock 4.4.4 factory image again and in the process unlocked the bootloader as of now.
But there is no change in the situation. I love this tablet and I am desperate to get this sorted out. Please help me.
Click to expand...
Click to collapse
Clonazepam - Our sincerest apologies in regards to the issues you're having with your Nexus 7. Please send us an emailed description of the issue along with your Nexus' serial number to [email protected] and we will assist you as best as possible.

Asus_USA said:
Clonazepam - Our sincerest apologies in regards to the issues you're having with your Nexus 7. Please send us an emailed description of the issue along with your Nexus' serial number to [email protected] and we will assist you as best as possible.
Click to expand...
Click to collapse
I bought the tablet in India and I still live in India. Will you be able to assist me here?

ems328i said:
I am in the same situation. I got my device back from Asus repair today, it was unlocked and running a custom KitKat rom, but only the screen was broken and that was what was repaired (at my own expense).
I turned it on and it was stuck at the 4 swirling dots for more than 20 mins, so I wiped the device completely in TWRP and tried to flash a stock factory image (Lollipop) - same problem. I tried flashing a factory KitKat image, also stuck at boot animation.
I then re-flashed TWRP since it had been replaced by the stock recovery, and then sideloaded a custom Lollipop rom (Screwd) - still same problem.
It is strange that I can use adb and fastboot, but nothing gets past the swirling dots. Hopefully someone can point us both in the right direction....
Click to expand...
Click to collapse
Did you update the bootloader to 04.14 ? It is required to update the bootloader to run lolipop. Try flashing the new bootloader.IMG and then installing stock or custom lolipop ROM.

str1ker0ne said:
Did you update the bootloader to 04.14 ? It is required to update the bootloader to run lolipop. Try flashing the new bootloader.IMG and then installing stock or custom lolipop ROM.
Click to expand...
Click to collapse
Yes, I had updated the bootloader. I have now RMA'd again....

ems328i said:
Yes, I had updated the bootloader. I have now RMA'd again....
Click to expand...
Click to collapse
All I can suggest right now is try a different ROM like aosp or cm official. You seem to be doing everything correctly. You can also try flashing the original 4.3 factory image with 03.14 bootloader maybe it'll boot. Then revert back to lolipop.

str1ker0ne said:
All I can suggest right now is try a different ROM like aosp or cm official. You seem to be doing everything correctly. You can also try flashing the original 4.3 factory image with 03.14 bootloader maybe it'll boot. Then revert back to lolipop.
Click to expand...
Click to collapse
Thanks but as I mentioned I have RMA'd it again so i don't have it anymore...

ems328i said:
Thanks but as I mentioned I have RMA'd it again so i don't have it anymore...
Click to expand...
Click to collapse
Hopefully they won't charge you this time.

bump to original question

[Q] Secure Booting Error! Cause: boot certification verify

Hi, I am new to the whole root/custom recovery scene so don't really know what I'm doing, so I tried to use Flashify to flash TWRP on to my international LG G3 running 5.0 (rooted). Unfortunately, when booting into recovery I got a small message in the corner saying Secure booting error! Cause: boot certification verify, before my phone screen went black and my led started flashing blue and red. Holding down the vol - button seemed to fix it and the phone still boots fine, but it does this every time I try to boot into recovery. I just want to play around with custom ROMs and TWRP
Anyone got a fix for this, or know what is going on (bearing in mind that I am a complete noob with this stuff)?
Thanks in advance

Adlephix said:
Hi, I am new to the whole root/custom recovery scene so don't really know what I'm doing, so I tried to use Flashify to flash TWRP on to my international LG G3 running 5.0 (rooted). Unfortunately, when booting into recovery I got a small message in the corner saying Secure booting error! Cause: boot certification verify, before my phone screen went black and my led started flashing blue and red. Holding down the vol - button seemed to fix it and the phone still boots fine, but it does this every time I try to boot into recovery. I just want to play around with custom ROMs and TWRP
Anyone got a fix for this, or know what is going on (bearing in mind that I am a complete noob with this stuff)?
Thanks in advance
Click to expand...
Click to collapse
I believe you need to use imageprep.

BR7fan said:
I believe you need to use imageprep.
Click to expand...
Click to collapse
Are you sure it'll be safe, given my current situation? I was led to believe it was an error that I'd only be able to fix with a factory reset.

Adlephix said:
Are you sure it'll be safe, given my current situation? I was led to believe it was an error that I'd only be able to fix with a factory reset.
Click to expand...
Click to collapse
I have used this method and had no issues. The reason you can't flash it with flashify is because it only works on KitKat for lg g3. People using lollipop has to use image prep method. There should be two tutorials,one for going back to kitkat and one for alowing you to flash it while on lollipop.

BR7fan said:
I have used this method and had no issues. The reason you can't flash it with flashify is because it only works on KitKat for lg g3. People using lollipop has to use image prep method. There should be two tutorials,one for going back to kitkat and one for alowing you to flash it while on lollipop.
Click to expand...
Click to collapse
OK, just had a read of the Imageprep post and this all seems completely beyond me. Is there an alternative method, or if not, could someone simplify what I'd need to do with Imageprep to get TWRP working on 5.0?

Adlephix said:
OK, just had a read of the Imageprep post and this all seems completely beyond me. Is there an alternative method, or if not, could someone simplify what I'd need to do with Imageprep to get TWRP working on 5.0?
Click to expand...
Click to collapse
This is the easiest one that I know of. Just read carefully and you'll be fine.

[LG G Pad 7.0 v410] Custom boot.img not working

xdadev won't let me post this in lg g pad 7.0 forums (too new) so have to post here. Maybe similar on g pad 8.3
I created a custom boot.img (small edit, replaced /sbin/chargerlogo with /system/bin/reboot with Android Kitchen), but whenever I try to flash the boot.img (with Rashr, after correcting the permissions) and reboot, it sticks on the LG logo and there is an error at the top ("Error: boot verification failed"). Same issue using cofface's unpack/repacker for kernel.
I noticed the boot.img I create using any method is always less than half the file size of the stock image boot.img. Something isn't adding up, anyone know possible why?
I can boot up to TWRP and restore the boot, but anyone have a suggestion on why the boot.img might not be working?
Maybe I have to unlock the bootloader? Anyone know how to do that on this device?
I'm not sure I'm even asking the right questions here, any lead is greatly appreciated!

same exact thing
roleyus said:
xdadev won't let me post this in lg g pad 7.0 forums (too new) so have to post here. Maybe similar on g pad 8.3
I created a custom boot.img (small edit, replaced /sbin/chargerlogo with /system/bin/reboot with Android Kitchen), but whenever I try to flash the boot.img (with Rashr, after correcting the permissions) and reboot, it sticks on the LG logo and there is an error at the top ("Error: boot verification failed"). Same issue using cofface's unpack/repacker for kernel.
I noticed the boot.img I create using any method is always less than half the file size of the stock image boot.img. Something isn't adding up, anyone know possible why?
I can boot up to TWRP and restore the boot, but anyone have a suggestion on why the boot.img might not be working?
Maybe I have to unlock the bootloader? Anyone know how to do that on this device?
I'm not sure I'm even asking the right questions here, any lead is greatly appreciated!
Click to expand...
Click to collapse
i also have an lg glad 7.0 att v410 running 5.0.2 the only was i could root it was if i used root king and that was all i could do. I'm despretly trying to unlock the boot loader for days now and no success. SAME THING ERROR BOOT CERTIFICATION VERIFY. I DID FIND THAT IF I USE THE TWRP 2.8.5.0 FOR V400 NOT V410 FLASH TO RCOVORY VIA FLASHILY AND WHENI REBOOT ITS IN FASTBOOT MODE. SO I THINK THATS THE 1ST STEP IN ULOCKING THE BOOTLOADER NOT SURE THOUGHT I NEED HELP TO NAD NO ONE ON THE INTERNET KNOWS. sorry i guess i hit caps lol

Maybe you can help
Im probably digging in a graveyard here but i accidently flashed my boot instead of recovery in twrp. Well now im screwed i can still get into twrp with full functionality however i need the original boot.img or a boot.img that will boot up my Tablet. I have an Lg Gpad 7.0 LTE V410 but im assuming i need a new boot file to flash as i have screwed mine up. But please any help will be so appreciated as i can not do anything without it. I can get to twrp without an issue and download mode without an issue. Thank you in advance

Same here
Did you find a way to solve it?

LG G4 Bootloop on first day - Unlocked bootloader can't return -.-

Bought a Refurbished LG G4, unlocked the bootloader then hour later it switched off and now its doing a bootloop, not sure if its a main board problem which this phone is notorious for or not, I had a custom root on it and rooted, so when I boot up it goes to the lg screen with it saying in top left bootloader unlocked, then after 10 seconds it goes to the animated lg splash screen but only for like 3 seconds then boots off, from what i've seen in other people bootlopp that it does not make it to the second screen, Am i having the same issue?
Also I literally can't take it back due to me messing with it, have I literally just lost the £250 I paid?
Phone does not go into recovery and if it did some reason it goes to the stock one (before it bootlooped) goes into download mode but only for a few seconds then boot loops again

You've lost only 250, when I got mine it cost me 480 ! Anyway I kinda fixed mine. I have downgraded it to 5.1, phone did not boot up so directly after that I disabled the two big cores ( https://www.reddit.com/r/lgg4/comments/45gfg2/dae_g4_series_msm_big_core_disable_tool_guide/ ), even though I disabled only two cores the phone boots up only on one!! so its pretty laggy but when you flash custom recovery you can root it and via devices manager enable all 4 cores as phone works almost as normal, or you can even flash a custom ROM as I did. If you flash any cm based or aosp based rom , the base of a firmware tells it that the phone has only 4 cores so you can still use it as normal on 4 cores. However if you flash any stock based ROMs it will turn the 2 cores you've disabled back on again and it will not boot up. I'm running AOSP SUPERXE ROM since about two weeks.

How do you downgraded if the phone bootloops? I can't even go to recovery mode

chavocarlos said:
How do you downgraded if the phone bootloops? I can't even go to recovery mode
Click to expand...
Click to collapse
I know you said it won't go in twrp but just try this-
Turn phone off
Hold volume down and power
When lg logo appears let go of power and repress and hold
It should show a menu to wipe the device just click yes and then yes again for confirmation it should then boot into twrp if not and it wipes your phone at least you can start again with stock....

vvvvvvvvvvvvvvvvvvvv
Adam Myczkowski said:
You've lost only 250, when I got mine it cost me 480 ! Anyway I kinda fixed mine. I have downgraded it to 5.1, phone did not boot up so directly after that I disabled the two big cores ( ), even though I disabled only two cores the phone boots up only on one!! so its pretty laggy but when you flash custom recovery you can root it and via devices manager enable all 4 cores as phone works almost as normal, or you can even flash a custom ROM as I did. If you flash any cm based or aosp based rom , the base of a firmware tells it that the phone has only 4 cores so you can still use it as normal on 4 cores. However if you flash any stock based ROMs it will turn the 2 cores you've disabled back on again and it will not boot up. I'm running AOSP SUPERXE ROM since about two weeks.
Click to expand...
Click to collapse
intresting, you got skype or something i can ask few questions,
Do i have to downgrade before trying that program? i tired it and it got to 100% and done it whatever but still does not boot, is there anything else i need to do? regards

whelan1899 said:
intresting, you got skype or something i can ask few questions,
Do i have to downgrade before trying that program? i tired it and it got to 100% and done it whatever but still does not boot, is there anything else i need to do? regards
Click to expand...
Click to collapse
You can text me on Hangouts if you want, but I can tell you that you have to downgrade to 5.1 first, they files from the G4 zip are only for Lollipop
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
chavocarlos said:
How do you downgraded if the phone bootloops? I can't even go to recovery mode
Click to expand...
Click to collapse
Simply via LG UP, you can still access download mode !

Adam Myczkowski said:
You can text me on Hangouts if you want, but I can tell you that you have to downgrade to 5.1 first, they files from the G4 zip are only for Lollipop
---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------
Simply via LG UP, you can still access download mode !
Click to expand...
Click to collapse
got a kdz file no idea if it was 5.1 or not
UK H81510B_00 is the name of it, will try do that and see, is the tot version for my version available?

whelan1899 said:
got a kdz file no idea if it was 5.1 or not
UK H81510B_00 is the name of it, will try do that and see, is the tot version for my version available?
Click to expand...
Click to collapse
Make sure you have H815 first! And yes its 5.1 - 10 stands for first release and G4 has been released with 5.1, if there was 20 instead it would be 6.0. I don't actually think there's any tot file. BTW when you downgrading to 5.1, open LG Up, select 'upgrade' and choose the kdz, then close it down and open up again. You should see that the file's location is still there so click on the 'refrubrish' and then start. Phone probably will not boot up still, so turn it off and flash the file from G4.zip

Adam Myczkowski said:
Make sure you have H815 first! And yes its 5.1 - 10 stands for first release and G4 has been released with 5.1, if there was 20 instead it would be 6.0. I don't actually think there's any tot file. BTW when you downgrading to 5.1, open LG Up, select 'upgrade' and choose the kdz, then close it down and open up again. You should see that the file's location is still there so click on the 'refrubrish' and then start. Phone probably will not boot up still, so turn it off and flash the file from G4.zip
Click to expand...
Click to collapse
on my box it says h815

Adam Myczkowski said:
Make sure you have H815 first! And yes its 5.1 - 10 stands for first release and G4 has been released with 5.1, if there was 20 instead it would be 6.0. I don't actually think there's any tot file. BTW when you downgrading to 5.1, open LG Up, select 'upgrade' and choose the kdz, then close it down and open up again. You should see that the file's location is still there so click on the 'refrubrish' and then start. Phone probably will not boot up still, so turn it off and flash the file from G4.zip
Click to expand...
Click to collapse
urmm I was doing it wrong haha was upgrading it, done what you said and it flashed and rebooted to the screen
do i still need to deactivated the cores and install a rom, or will it somepoint do the same thing?

whelan1899 said:
urmm I was doing it wrong haha was upgrading it, done what you said and it flashed and rebooted to the screen
do i still need to deactivated the cores and install a rom, or will it somepoint do the same thing?
Click to expand...
Click to collapse
Yes, better if u do that, phone get brick at any time still and you don't really need to flash any custom ROM, just flash recovery and supersu via it, then download the device manager and by changing the frequency enable all 4 cores, unless you really want to flash custom rom, but remember any stock based ROMs will re-enable all six cores what will lead to a bootloop again.