i want to sell my lg g pro but the problem is that when i power it i get on lg screen "booting error,deveice unlock so booting" and people start to think that the phone have problems so it wont sell!!
i want the message to disappear ,is there any way to do that? if not how can i relock my bootloader to remove the error ?
i used freegee to get to cmwr and twrp
apart from the message the phones works and boots fine 100%
thanks
Restore to stock and this error will disappear! Is not anything to worry about.
hypnz said:
Restore to stock and this error will disappear! Is not anything to worry about.
Click to expand...
Click to collapse
what do you mean restore to stock the rom or the boot loader ?
If you restore to stock will restored and the boot loader.
Related
Hi
I had stock room+root and got massage about firmware update, I dl it and try to update. My device rebooted and show for few second: secure booting error cause: device unlock!, so boot success! And than entering to the twrp (v2.6.3.0). Now everytime when I tring to power on my g pad happen the same.
Any idea how to repair it? Im stuck. I tryied reinstal rom and done full wipe, but nothink changed.
Sorry for my bad english :/
ekterion said:
Hi
I had stock room+root and got massage about firmware update, I dl it and try to update. My device rebooted and show for few second: secure booting error cause: device unlock!, so boot success! And than entering to the twrp (v2.6.3.0). Now everytime when I tring to power on my g pad happen the same.
Any idea how to repair it? Im stuck. I tryied reinstal rom and done full wipe, but nothink changed.
Sorry for my bad english :/
Click to expand...
Click to collapse
I think that you were not supposed to use TWRP 2.6.3.0. The correct version is 2.6.3.2. Not sure how to fix your current problem, though.
this message is normal to see if you have twrp installed and try to enter recovery or if you have cyanogen mod 11. Also update your twrp with version 2.6.3.2
katsika said:
this message is normal to see if you have twrp installed and try to enter recovery or if you have cyanogen mod 11. Also update your twrp with version 2.6.3.2
Click to expand...
Click to collapse
Except he says he sees the message every time he power's on the phone. Does CM do that?
woody1 said:
Except he says he sees the message every time he power's on the phone. Does CM do that?
Click to expand...
Click to collapse
yes its normal if you have cm11 to see this message everytime you boot the gpad, it just means that loki is working. Now if he has stock rom it isnt normal to see this message except for when he does the button combo to enter recovery.
I followed the tutorial at http://forum.xda-developers.com/showthread.php?t=2762171 to install KK ROM on my OG E977, did EXACTLY like written, but then I got stuck at boot screen telling me I have a boot security error, probably due to a locked bootloader, I guess. I try to flash the stock KDZ firmware but KDZ updater offline fix tells me battery level is low when it's not, even when the battery was fully charged.
I can't switch off the phone manually, because it starts again and gets stuck at the LG logo screen with this message:
Secure booting Error!
Cause: boot certification verify
The only way to turn the phone off is with CWM touch recovery 6.0.4.8 by LGviet (after installing the Sling KK ROM or the F180 patch, I guess, because the recovery utility was CWM 6.0.4.7 non-touch installed by FreeGee after unlocking the bootloader.). And when I turn the phone off and plug the charger, the phone boots up by itself and gets stuck at boot security error screen.
I tried to send a CyanogenMod ROM via adb sideload, but it tells me the ROM is for E975, while the phone is a F180 model.
Could someone give me a help, please? Thanks in advance.
ksio89 said:
I followed the tutorial at http://forum.xda-developers.com/showthread.php?t=2762171 to install KK ROM on my OG E977, did EXACTLY like written, but then I got stuck at boot screen telling me I have a boot security error, probably due to a locked bootloader, I guess. I try to flash the stock KDZ firmware but KDZ updater offline fix tells me battery level is low when it's not, even when the battery was fully charged.
I can't switch off the phone manually, because it starts again and gets stuck at the LG logo screen with this message:
Secure booting Error!
Cause: boot certification verify
The only way to turn the phone off is with CWM touch recovery 6.0.4.8 by LGviet (after installing the Sling KK ROM or the F180 patch, I guess, because the recovery utility was CWM 6.0.4.7 non-touch installed by FreeGee after unlocking the bootloader.). And when I turn the phone off and plug the charger, the phone boots up by itself and gets stuck at boot security error screen.
I tried to send a CyanogenMod ROM via adb sideload, but it tells me the ROM is for E975, while the phone is a F180 model.
Could someone give me a help, please? Thanks in advance.
Click to expand...
Click to collapse
How can you boot into recovery once it's in Secure booting error?
Any how fix it using teeny bin repair, it's easy fix.
Ahmed Xperia p said:
Any how fix it using teeny bin repair, it's easy fix.
Click to expand...
Click to collapse
Or, just as an alternative, find a KDZ that works with the regular KDZ Updater (filesize up to 1.17GB worked for me). This way, as opposed to the offline method with LG Support Tool, you won't get a low battery error, even if the battery is completely dead. Had exactly the same problem myself, this was the solution I used.
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
First, let me start off by saying I'm an idiot; my phone was stuck in a bootloop and out of panic I tried to fix the problem and only made it worse. Now I'm left with no OS installed and I'm stuck at my custom recovery.
I am using twrp as my custom recovery and I'm able to use my mac to send files successfully to my phone. The problem arises when I try to flash the zip and I am prompted with the message that says that the file is corrupted. I tried installing multiple zip files onto my phone and when returning it to stock did not work I even tried to flash Cyanogen Mod. Each time I was greeted with the same message.
This sucks because I just bought my nexus 5x and I don't want to lose it to a stupid mistake. If anyone could help in anyway that would be amazing. If not I will still accept prayers for my potentially dead phone.
-Carlos
Edit: problem solved. I did what you guys said and returned to stock and didn't panic. Thanks so much.
you mean the unlocked bootloader message? thats nothing
or maybe the md5 message, which also is normal?
to me sounds like you are panicking for no reason, but anyway, search for nexus root toolkit, install it, and choose the option to revert stock + unroot
Giorgos Chatziioannou said:
you mean the unlocked bootloader message? thats nothing
or maybe the md5 message, which also is normal?
to me sounds like you are panicking for no reason, but anyway, search for nexus root toolkit, install it, and choose the option to revert stock + unroot
Click to expand...
Click to collapse
Yeah as said above there is no need for panic.
Even if your recovery wont flash the zips you can flash the stock factory images via fastboot manually (i dont now if its available on mac if not boot a linux live disk).
And if your bootloader is still locked unlock it reboot to bootloader and then flash the images.
By the way you should provide more information such as os details twrp version bootloader state and so on...:fingers-crossed:
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
So I tried sideloading. I was able to get into the stock recovery. I tried wiping cache and data, then tried installing the newest stock rom.
Everything seemed to work. Then I had to restart. A message popped up after the same "Your device software can't be checked for corruptions. Please lock the bootloader". It had the title in blue stating "Encryption unsuccessful".
Then said, "Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
Then there is a single button that says, "Reset Phone".
Problem still persists.
Help please...
Why did you bought a bootlooped phone?
Sin Stalker said:
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
Click to expand...
Click to collapse
When my Nexus 5x got into bootloop, I sent it to LG and they had to change the whole circuit. So yeah.
When you flash Google Factory Image, it flash the stock kernel.
If you have warranty, then send it to Google/LG. If you haven't got, then you're in problem. New motherboard needed, but it's expensive.
See the following thread for more info.
https://forum.xda-developers.com/nexus-5x/help/5x-bootloop-cause-fix-t3476794/
khalifakk said:
Why did you bought a bootlooped phone?
Click to expand...
Click to collapse
Cause its cheaper.
Sin Stalker said:
Cause its cheaper.
Click to expand...
Click to collapse
Then face the consequences...
khalifakk said:
Then face the consequences...
Click to expand...
Click to collapse
What consequences?
Hardware bootloop can't be fix by software.
Duckscreen said:
Hardware bootloop can't be fix by software.
Click to expand...
Click to collapse
Exactly. Everyone has either been able to get a replacement under warranty or was pretty much screwed if it was out of warranty.
Sent from my Nexus 5X using Tapatalk
Sin Stalker said:
What consequences?
Click to expand...
Click to collapse
A bootlooped phone for ever....
I recommend you will install kernel adiutor app after try rooting
I recommend you will install kernel adiutor app after try rooting
Almost I got no bootloop even no random reboot nexus 5x's state