• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [MetroPCS] ERROR: "Boot Certification Verify"

CaseyRockStar

CaseyRockStar

Member
Hiya,

MS500 F6, definitely rooted (though I've suspected my bootloader is not unlocked, is that possible?)

Normal boot and all operations are fine, but every time I try to Boot into recovery or flash anything, I get this:



--------------------------------------------
Secure booting Error!
Cause: boot certification verify
--------------------------------------------
as seen here:
GqzBsoA.png

(pardon my flash)​


It's stuck on that logo splash screen, actually have to remove the back and battery ... but then it boots up fine.

I've been customizing the old-fashioned way, and I finally got the phone where I like it.

So all I really wanna do is flash Freedom kernel ....



I appreciate any help!!!



Thanks!


(QUESTION ALSO ASKED HERE, IN L70 room, they had a similar thread)
http://androidforums.com/threads/tool-lg-laf-recovery-multitool-v1-2.863389/page-5#post-6894219
 
UNBRICK? What do you mean? Phone works fine ... it's fully functional and properly rooted. It turns on and off and boots normally perfectly well.

Only problem is I want to flash GameTheory's Freedom kernel, and I can' do it (hmmm, GameTheory himself likes your "burn the crops and salt the earth" advice).



I appreciate your time and and advice, you know far more than I do. And I know you have no incentive to do so, but I'm gonna need a lot more convincing before I go to those lengths.
 
CaseyRockStar said:
It's stuck on that logo splash screen, actually have to remove the back and battery ... but then it boots up fine.
Click to expand...
^^ This statement makes it sound like you get a bootloop and why Viperdink suggested unbricking to fully restore which under that circumstance he made a good call.

Well it's late so I'll try to chime in tomorrow... Well later today lol. I'm sure the good folks here will reply to you before then though.
 
:wtfdroid:
Normally I'd advice you to try some very helpful apk's like;
Game Theory's Rebooter app, Playful Gods rebooter app, or Quickboot app, To enter into recovery.
Since you want the " Old Fashion Way " try reading this,
http://forum.xda-developers.com/showthread.php?t=2131284
Then after YOU Diddle around with your device for Hours and after YOU come to the conclusion YOU did something wrong , take 18 minuets and,
:spitoutdroid:UNBRICK.

(ps; ROFLMFAO):D:):cool:
 
It seems to me like all he's done is root and delete some bloat apps, and install a custom recovery. Judging by the problems he is having it seems like he installed a recovery built for a different device. If this is the case then his phone probably isnt loki'd which is why he gets the security error. Its easy to forget that the f6 does come with a locked bootloader. If my suspicions are correct then installing Hroark13's TWRP or Pressy4pie's CWM may fix the problem.
 
I have had more experience with CWM (just installing ROMs).. and.. As an artist and eccentric type person... I love rainbow mode...

But, the simplicity and straightforwardness of TWRP... has taken allot of mystery and ignorance out of the whole process of doing things correct....

And the touch works.... CWM touch is something of a myth to me.. it didn't work on the admire or the premia..
 
CYCONUMNUM said:
I have had more experience with CWM (just installing ROMs).. and.. As an artist and eccentric type person... I love rainbow mode...

But, the simplicity and straightforwardness of TWRP... has taken allot of mystery and ignorance out of the whole process of doing things correct....

And the touch works.... CWM touch is something of a myth to me.. it didn't work on the admire or the premia..
Click to expand...
I can think of two times that TWRP's file manager has gotten me out of a bootloop without a factory reset or flashing a rom over again. Once it was because of a bad boot animation and once because of an Xposed module. In both cases I just deleted the file that was causing the problem. If I had CWM installed and not TWRP I'd have had to factory reset and flash the rom all over again.
 
To remove a file or app causing bootloop without a recovery. Just change the path to its location...
Bash: 
adb shell
adb rm /system/app/file_name.apk

To add file that was accidentally removed and causing bootloop. Open terminal to where file is located...
Bash: 
adb push file_name.apk /system/app

And I always run the following when I'm done using shell...
Bash: 
adb kill-server

These are good to know since not every phone gets a TWRP recovery.
 
GameTheory said:
To remove a file or app causing bootloop without a recovery. Just change the path to its location...
Bash: 
adb shell
adb rm /system/app/file_name.apk

To add file that was accidentally removed and causing bootloop. Open terminal to where file is located...
Bash: 
adb push file_name.apk /system/app

And I always run the following when I'm done using shell...
Bash: 
adb kill-server

These are good to know since not every phone gets a TWRP recovery.
Click to expand...
That is good to know but if the phone won't boot up all the way how do I get it to receive these commands? Is this something I could do while booted into cwm or stock recovery?
 
Masterchief87 said:
That is good to know but if the phone won't boot up all the way how do I get it to receive these commands? Is this something I could do while booted into cwm or stock recovery?
Click to expand...

You can be stuck in a bootloop and still run these commands. This is how I recover my phone when I'm experimenting and get bootlooped or bricked.

Oh and from a bootloop or brick you can go to recovery like this...
Bash: 
adb reboot recovery
 
Last edited:
GameTheory said:
You can be stuck in a bootloop and still run these commands. This is how I recovery my phone when I'm experimenting and get bootlooped or bricked.

Oh and from a bootloop or brick you can go to recovery like this...
Bash: 
adb reboot recovery
Click to expand...
Thanks I didn't know you could use those commands while stuck at the boot screen. I'll try it out next time I get a bootloop and know what's causing it.
 
CaseyRockStar said:
MS500 F6, definitely rooted (though I've suspected my bootloader is not unlocked, is that possible?)
Normal boot and all operations are fine, but every time I try to Boot into recovery or flash anything, I get this:
--------------------------------------------
Secure booting Error!
Cause: boot certification verify
--------------------------------------------
It's stuck on that logo splash screen, actually have to remove the back and battery ... but then it boots up fine.​
Click to expand...
The bootloader on MS500 is indeed locked. To boot a custom rom or recovery, the boot image or recovery image on the F6 needs to be loki'fied. All boot images and recoveries released by developers in the forum should be properly loki'fied already. So like Masterchief87 said, you either used a recovery not from this forum (thus not properly loki'fied) or your recovery image is corrupt. "Boot certification verify" sounds like your recovery image doesn't pass the signature check, so the phone's bootloader won't load the kernel and you're stuck until you pull the battery (kinda like a kernel panic except in this case the kernel is not even loaded).

Since you're still able to boot normally, do not overwrite your boot image until you make sure your recovery is working. Like Masterchief87 suggested, find hroark13's TWRP and install that. The apk should put the properly loki'fied TWRP recovery image at the recovery partition.

If for some reason you're unable or unwilling to install the apk to your /system partition, you can pull the image file (with extension .lok) from the apk and manually install it to the recovery partition (so the boot and /system partitions remain unchanged). If you really need to do that, I can give you the commands, but it's easier to just use the apk (which includes the ability to reboot to recovery within the app) nicely packaged by hroark13. Good luck.
 
Okay here goes......i have the lg optimus f6 by MetroPCS now I see all of the new ROMs and all the Older ROMs getting updates to them now where do I need to start so I don't actually overdue my phones. Capabilities
 
If all he did was install a recovery that wasn't made for the f6 then he could probably just install the correct one. Then if that doesn't work reflashing the stock kdz firmware would be the plan b. The only reason it wouldn't be plan a is to avoid having all changes to /system being undone.
 
GameTheory said:
@drtbikace69

Quick Outline...
1. install root and twrp recovery from HERE
2. make a backup in twrp recovery
3. pick a rom and install it
4. simple, easy, done!
Click to expand...
Whats your personal opinion on the best rom available for my (p.o.s.) phone. im headed to get get a 32gb sd because i only have a 16g in there now. Im wanting to switch my straighttalk service to this phone. But wanted to update Rom first. Im wanting to make this phone to be music games and apps only with no limitations as far as compatible and memory sufficient. Hope im not being a nuisance to you or Dastardly Muffin or anyone else for that matter. Thanks in advance
 
You must log in or register to reply here.
Back
Top Bottom