Develop Bugs

[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.

LGG4 Unable to boot recovery twrp or boot by using power /vol buttons

Hi at the moment i am unable to boot into recovery either by using twrp or the lgg4 power /vol down method also adb is seeing my phone as unauthorised so unable to reflash recovery that way do not know why this has come about as it has been fine im am running genysis 3.4 rom xposed addition i dropped my phone today but can,t see that having to much of an affect, also when i use the lgg4,s manual reboot to recovery method it justs restarts the phone normally where as it used to boot to twrp any guidance would be most welcome.

tye69 said:
Hi at the moment i am unable to boot into recovery either by using twrp or the lgg4 power /vol down method also adb is seeing my phone as unauthorised so unable to reflash recovery that way do not know why this has come about as it has been fine im am running genysis 3.4 rom xposed addition i dropped my phone today but can,t see that having to much of an affect, also when i use the lgg4,s manual reboot to recovery method it justs restarts the phone normally where as it used to boot to twrp any guidance would be most welcome.
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to right Q&A to get expertise help on the issue.
-Vatsal

tye69 said:
Hi at the moment i am unable to boot into recovery either by using twrp or the lgg4 power /vol down method also adb is seeing my phone as unauthorised so unable to reflash recovery that way do not know why this has come about as it has been fine im am running genysis 3.4 rom xposed addition i dropped my phone today but can,t see that having to much of an affect, also when i use the lgg4,s manual reboot to recovery method it justs restarts the phone normally where as it used to boot to twrp any guidance would be most welcome.
Click to expand...
Click to collapse
If you rooted:
https://play.google.com/store/apps/details?id=com.davidjr621.rebooter
If no:
https://www.youtube.com/watch?v=mCxJ5k8vWEI

Today's CM14 bricked my H815 (no bootloader, no fastboot, no recovery)

Hi,
My H815 always suffered from this problem: http://forum.xda-developers.com/g4/help/fastboot-download-mode-problem-t3466649 - the only way I could have fastboot was from an adb shell.
Well, that was not a problem until today: CM14's nightly broke (booting just loops at the moving logo) and now I have no way to go back to fastboot. And if I try the recovery mode, I just have a blurry circle saying "erasing" for a few seconds, then a looping CM logo.
Anyone has a way out of this mess ?

bestouff said:
Hi,
My H815 always suffered from this problem: http://forum.xda-developers.com/g4/help/fastboot-download-mode-problem-t3466649 - the only way I could have fastboot was from an adb shell.
Well, that was not a problem until today: CM14's nightly broke (booting just loops at the moving logo) and now I have no way to go back to fastboot. And if I try the recovery mode, I just have a blurry circle saying "erasing" for a few seconds, then a looping CM logo.
Anyone has a way out of this mess ?
Click to expand...
Click to collapse
When you say you try the recovery mode how do you try to get into it? Btw do you have twrp installed?

Same thing happened to me, tried to install, just got put straight back in to TWRP after boot. Tried installing a stock ROM, CM ROM & using LG Bridge to recover, to no avail. Help appreciated, (i'm assuming LGUP is going to come up a lot)

Tycoon282 said:
Same thing happened to me, tried to install, just got put straight back in to TWRP after boot. Tried installing a stock ROM, CM ROM & using LG Bridge to recover, to no avail. Help appreciated, (i'm assuming LGUP is going to come up a lot)
Click to expand...
Click to collapse
The OP has another issue pls do not hijack.

steadfasterX said:
The OP has another issue pls do not hijack.
Click to expand...
Click to collapse
Sorry, it's nearly the same issue though, CM14.1 broke phones today.

Today's update broke mine as well. Looking for solutions. Will follow your thread and progress.

Same for me. Tried download mode with lgup to flash stock which worked once - but I kind of bricked it again by trying to install cm14.1 again. Then i tried to go back to stock using lgup again, but now lgup it just crashes. The phone now goes automatically to download mode after turning it on, the progress bar stays at 0%, the phone says "633A B100" and lgup crashes after 9% "prepare dlmode" or something similar. any ideas? :/

Some people seem to have fixed this issue by flashing the official Cyanogenmod Recovery.

thewild said:
Some people seem to have fixed this issue by flashing the official Cyanogenmod Recovery.
Click to expand...
Click to collapse
After flashig the CM Recovery via TWRP, i can't use the recovery anymore. If i boot into CM-Recovery the display shows "Ereasing" and start the system. After that i got a bootloop.
Is it possible to use fastboot??

You guys should also check CM14.1 thread because people there are talking about the same problem. The latest post says the only solution was to flash an official kdz with LGUP.

thewild said:
You guys should also check CM14.1 thread because people there are talking about the same problem. The latest post says the only solution was to flash an official kdz with LGUP.
Click to expand...
Click to collapse
Did that. Worked once. Then i tried to flash cm again and had the same problems, so i wanted to flash stock again... now lgup crashes at 9% and the phones goes directly to download mode after turning it on.

onlyolli said:
Did that. Worked once. Then i tried to flash cm again and had the same problems, so i wanted to flash stock again... now lgup crashes at 9% and the phones goes directly to download mode after turning it on.
Click to expand...
Click to collapse
And the two times you tried to flash CM, that was with the same recovery ?
Can you go into fastboot mode ?

thewild said:
And the two times you tried to flash CM, that was with the same recovery ?
Can you go into fastboot mode ?
Click to expand...
Click to collapse
Yes, it was with cm recovery 20161130, if i remember correctly.
Sadly now, i can not go into fastboot. The phone goes directly into download mode. My windows vm detects the phone, and tries to flash a recent kdz, but lgup crashes at 9%. The phone still shows "0%".

Oh that's bad. What about another kdz ?

thewild said:
Oh that's bad. What about another kdz ?
Click to expand...
Click to collapse
Already tried like 3-4.... Its always the same. If the tool would at least give me a little bit more information, but it just stops.

I don't know then. Some users seem to have had the same problem (stuck at 9%) : http://forum.xda-developers.com/search/forum/4233?query=lgup 9%

I had the same issue, tried several things, my final solution was:
- Start in download mode (Volumen up and then plug in cable)
- use "LG Brigde" on Mac to install stock Rom ( Software update tab in APP ) guess should also work with Windows
- Boot original android
- enable usb debug
- Start bootloader via ADB
- fastboot flash recovery to twrp 3.0.2
- Boot in recovery via power and vol down (first factory reset from stock appears but after this twrp is starting)
- install cm nighty of 1 DEC via ADB sideload
- reboot and done
In the meantime i updated to twrp 3.0.2-1., installed gapps etc. everything is now working fine again.
Hope this is also working for you.

Which version of cm14 did u download and install? Can u please post the exact version?

Mmh ... LGUP is the Windows utility right ? How do I do if I only have a Linux machine ?

steadfasterX said:
When you say you try the recovery mode how do you try to get into it? Btw do you have twrp installed?
Click to expand...
Click to collapse
I'm trying to get to it via power+down, I get to the double "do you want to factory reset ?" question, but then :
- sometimes the CM recovery just says "erasing" for a few seconds and reboots to (non-working) CM
- sometimes it just plainly boots to (non-working) CM
I used to have TWRP installed but it didn't work with CM update, so I let CM install its own recovery.

TWRP BOOT LOOP has anyone found a solution (OTA update)

i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
[SOLVED]
went back to stock recovery and side loaded the full 1.4 gb rom i will leave a link for tutorial that i used, i wanted to get back to complete stock and this was the one use
"https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/"

When you have TWRP you have to install full zip, not simply the eval OTA zip

bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
Flash the stock recovery.
Get stock recovery from downloads.oneplus.net

I cant seem to flash the stock recovery. The device is not visible in adb devices or fastboot devices. im facing the same issue.

If you are using TWRP 3.0.4-0 - try a hard boot...hold down the power button for 20s...wait 20s, power it back on.

bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
easy solution. Boot into fastboot
download this tool.
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
if newest version isnt working, download an older version with older twrp
than unzip the tool and run the .bat file and install twrp.
Thats it

There are many posts on Nougat not working with official TWRP (based on 6.0 build). Try booting into stock recovery. performing a system settings reset, then booting into fastboot and run the adb command, <fastboot boot TWRP-3.0.2-1.28.img>. From there you can do virtually anything you need to do. I recommend at least using a modified version of TWRP (such as 1.28). This has been posted many times before, please try and do a search for the answers first, it will help tremendously. Thanks

recovery
i had the same problem on my rooted OP3 when i used TWRP 3.0.2-1 , it worked to flash the full 4.0.1 rom but failed for everything else, flashing latest verion of twrp fixed it for me

Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)

Aislandas said:
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Click to expand...
Click to collapse
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?

bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Noted that you solved your issue, but this post is about the new version of TWRP. Version 3.0.3 is available on twrp.me and it works with Nougat.

bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Gave up trying and booked a session with OP technicians Will see how it goes in a week.

[Solved] Was updating to Lineage OS 17 but now I'm stuck on stock Android 8

I have the G710EMW variant. As the title states, I was trying to install Lineage OS following sirbow2's thread 'Lineage OS 16/17/GSI Install Guide for LG G7 ULM'. Using the universal unlock method, I unlocked my phone. Next step was installing 21d ULM firmware; this is where I am stuck. When I begin the installation using LGUP, the phone boots into the rooted fastboot mode instead of the download mode. I even tried switching slots but it still boots up in fastboot mode.
Also, when I am able to load the download mode, it stays at the download mode screen & doesn't actually proceed further & neither is the device detected in device manager when it is connected in the download mode.
I've rooted quite a few phones in the past but this one has troubled me a lot. It is very difficult to find time for all this when you're working a full-time job. Please help me fix this. I'm happy even just to return to the stock LG ROM (which reminds me that the same thing happens when I try using the LG Bridge tool).
Thank you!

use this thread to flash stock https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303.

sinkoo1979 said:
use this thread to flash stock https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303.
Click to expand...
Click to collapse
Already tried that method. Everything works fine until the phone boots to start installation. Ideally it should start in download mode but in my case, it boots into the rooted bootloader.

@Awesomeslayerg was kind enough to message me this link (https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841) which helped me fix my problem.
Not only was I able to revert to stock; I went ahead to install LineageOS 17 which is amazing!
Thank you, Awesomeslayerg.
This thread can be marked as fixed now.