Hi all,
I just updated two G Pad 8.3 tablets to the recent weekly update of Lineage 14.1-20180422-NIGHTLY-v500. Both devices are identical to each other in terms of apps and set-up. On one devices the update went flawless and on the other I am stuck on the boot-screen. I can boot into TWRP (3.2.1-0). Is the only way to solve this a factory reset?
I would like to backup before but TWRP tells me there is not enough space even though the SD card would have enough. Weird!
I had a bricked tablet after I installed supersu in twrp...
"secure booting error
cause : boot certification verify"
So the solution was to use LG MOBILE SUPPORT TOOL and upgrade recovery, it installed 4.4.2 but then I put root, twrp and put lineage. So if you go to twrp, why dont you just wipe everything except twrp and then install a new rom, gapps.
Related
This morning my LG V500 offered a software update. I started the update process without thinking. When the tablet restarted to install the update I saw the LG logo and then was greeted with the following message on the screen:
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
...after which I end up at the TWRP screen.
This happens every time I restart the tablet.
Before the update, I had Android 4.2.2 installed with kernel v3.4.0. I had installed TWRP v2.6.3.1 to root my phone. I have NO custom ROMs installed.
I'd prefer not to restart from scratch, but I guess that I can do a Factory Reset, Advanced Wipe or Format Data from TWRP to restore functionality to my tablet.
Any ideas on how I can avoid losing all my customizations?
Cal_ab said:
This morning my LG V500 offered a software update. I started the update process without thinking. When the tablet restarted to install the update I saw the LG logo and then was greeted with the following message on the screen:
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
...after which I end up at the TWRP screen.
This happens every time I restart the tablet.
Before the update, I had Android 4.2.2 installed with kernel v3.4.0. I had installed TWRP v2.6.3.1 to root my phone. I have NO custom ROMs installed.
I'd prefer not to restart from scratch, but I guess that I can do a Factory Reset, Advanced Wipe or Format Data from TWRP to restore functionality to my tablet.
Any ideas on how I can avoid losing all my customizations?
Click to expand...
Click to collapse
What all have you tried?
A simple shut down and re-start possibly could fix it. Just a guess, but worth a try. You should update to TWRP's latest also.
same problem here
Same problem as original poster, just I was on 2.7.0.0 TWRP. Upgraded to 2.7.0.1 - same problem.
Restored from previous TWRP backup - same problem. Installed custom ROM - SAME PROBLEM!
Out of options at this point. HELP!
g---man said:
Same problem as original poster, just I was on 2.7.0.0 TWRP. Upgraded to 2.7.0.1 - same problem.
Restored from previous TWRP backup - same problem. Installed custom ROM - SAME PROBLEM!
Out of options at this point. HELP!
Click to expand...
Click to collapse
Ever since I rooted I've had that. In fact if you watch Ytube's video about rooting an LG G Tab, you will see guy say "Don't know what that is - but all works.
Now on a transformer101 I didn't see that.
But frankly, so what? You don't go to recovery that much -- that is the only time it shows.
Cal-123 said:
Ever since I rooted I've had that. In fact if you watch Ytube's video about rooting an LG G Tab, you will see guy say "Don't know what that is - but all works.
Now on a transformer101 I didn't see that.
But frankly, so what? You don't go to recovery that much -- that is the only time it shows.
Click to expand...
Click to collapse
Cal-123 - issue here is not just information message, but boot loop. No matter what I tried - it goes to main TWRP screen.
Looks like solution is here: http://forum.xda-developers.com/showthread.php?t=2622034&page=2 , will post update when done
Cal_ab said:
This morning my LG V500 offered a software update. I started the update process without thinking. When the tablet restarted to install the update I saw the LG logo and then was greeted with the following message on the screen:
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
Click to expand...
Click to collapse
I did a recovery with the LG tools. All my data was backed up so it wasn't a huge deal for me. I can't even remember why I rooted my GPad in the first place.
g---man said:
Cal-123 - issue here is not just information message, but boot loop. No matter what I tried - it goes to main TWRP screen.
Looks like solution is here: http://forum.xda-developers.com/showthread.php?t=2622034&page=2 , will post update when done
Click to expand...
Click to collapse
I Hope you worked things out, but your problem possibly could be that some Roms have a built-in recovery option - by that, I mean instead of just rebooting, they will boot into recovery. You might ck. that to see if it is enabled. This "SlimKat" ROM has the feature.
Good luck!
Cal-123 said:
I Hope you worked things out, but your problem possibly could be that some Roms have a built-in recovery option - by that, I mean instead of just rebooting, they will boot into recovery. You might ck. that to see if it is enabled. This "SlimKat" ROM has the feature.
Good luck!
Click to expand...
Click to collapse
Cal-123, thanks, I was restoring backup done with TWRP - same problem (rebooting to TWRP screen, not to system). Still don't know root cause, but problem was resolved by flashing stock KK update by using B2CApp. Obviously root is gone, so back to reading forum
At least can play Deer Hunter again
Cheers!
Hi guys,
I am currently stuck in a bit of a loop.
I'm running stock v30c on my D855, rooted using KingRoot and has the latest TWRP bumped.
I tried doing a test from one of the hidden menus, and now my device is stuck on:
"Secure Booting Error! Cause: boot certification verify"
This appears every time the device tried to boot to system, though TWRP works just fine!
Something else that's weird and has been happening since then is, that I cannot mount my phone using TWRP, it gets recognized as "USB Serial Device" (tried on a few computers).
Any suggestions? I'd rather not flash my device if it's not an absolute must.
Thanks.
So... after 3 hours of absolutely 0 response, I gave up and flashed my device with stock firmware.
After that I rooted it using KingRoot again and flashed TWRP using AutoRec.
Then restored my Nandroid backup.
Not the best solution, I did lose some data, at least I can use my phone now.
NEVER EVER touch those stupid hidden menus if you don't absuolutely must! Those might brick you to a level when you're going to have to lose some data!!
Glad I had the backup from a few days ago so it wasn't that bad.
Hi,
I tried to install cyanogenmod on my lg g4, bad idea...
It booted on loop on twrp.
So i tried to use "lg flash tool" and it dont work "connection to server failed".
Sorry for my bad english, i really need help.
Many tnx per advance
had the same, caused by the internal cm update procedure, see threat cm14 for details.
there is also the following procedure from, worked perfectly for me:
- in TWRP I wiped everything but internal and external storage
- connected phone to pc,put phone into bootloader and flashed LATEST CM-Recovery
- went into CM-Recovery and installed latest CM-Version
- then CM booted normaly
- now i just had to boot into bootloader again
- flash latest twrp recovery
- finaly flashing gapps via twrp
I can only get into download mode. Did you have the same problem too? From your post it sounds like you had access to TWRP the whole time
Hi guys,
For now I'm stuck on this error on updating to LineageOS (official repo). "secure booting error" me checked!
I used to do a clean Install nothing more than this. Only if things will load I flash GAPPS etc.*
Previously I've successfully flashed cm13 and cm14.1 and so on.
But sometimes I got the "secure booting error"
When flashing (custom) kernels I always get the "secure booting error".
On flashing roms sometimes it does sometimes it won't.
I'm not sure when or what went wrong or not.
I've never had issues to access twrp or flash twrp. Like I see on most topics.
So I'm pretty sure the problem exist in my bootloader.and not in the roms or other flashing. Maybe it isn't fully unlocked?
My LG G Pad 8.3 (v500) bought in The Netherlands.
I flashed V50020F Bootloader: https://www.androidfilehost.com/?fid=24352994023707804.
Flashing all went fine as far as tarp gives the right info. I only don't know how to check this.
TWRP: 3.0.x
Is there guide de to fix this? I've really spend days on this without any solution. It's really frustrated!
Hmm.. Same issue here.
Was on stable CM 14.1 & TWRP 3.0.2.0.
Flashed TWRP 3.0.2.2
Flashed Lineage experimental 14.1 & supersu addon zip
Rebooted and am stuck with the same secure boot error. I don't understand why I can't get into the same TWRP recovery I was just in to attempt to clean flash a nightly LineageOS 14.1.
------------
Here we go: https://forum.xda-developers.com/showpost.php?p=70740190&postcount=84
Follow those steps to get into TWRP.
Xenosis said:
Hmm.. Same issue here.
Was on stable CM 14.1 & TWRP 3.0.2.0.
Flashed TWRP 3.0.2.2
Flashed Lineage experimental 14.1 & supersu addon zip
Rebooted and am stuck with the same secure boot error. I don't understand why I can't get into the same TWRP recovery I was just in to attempt to clean flash a nightly LineageOS 14.1.
------------
Here we go: https://forum.xda-developers.com/showpost.php?p=70740190&postcount=84
Follow those steps to get into TWRP.
Click to expand...
Click to collapse
Don't use supersu with cm/lineage.
The secure boot error can be fixed by flashing this zip in recovery.
https://www.androidfilehost.com/?fid=95916177934554766
Thanks. Ya I had no idea there was a set of flashable su's for LineageOS in Extra.
Got it working. The issue was mostly that I had no idea how to use the hardware buttons for this tablet to get into recovery.
Thanks that helped me out!!
My Problem:
Lineageos 14.1 and Magisk 17.1 installed, updated Lineageos to actual nightly and got a
Secure booting error, Cause : boot certification verify
Solved with:
Boot into recovery mode with TWRP installed
Howto here: https://youtu.be/uo3YfszOPsQ
Than installed: v500-loki-kernel-to-bumped-kernel-signed.zip
Here is the proper thread with backround information
https://forum.xda-developers.com/showpost.php?p=60092491&postcount=1
Fixed it. Great job
[V500] "Secure Booting Error..." solution howto
Let me recap here, 'cause I get trapped in this issue every other year and it takes me a while to retrace back the steps for the solution.
Some intro, for starters: I have been running Lineage OS on my device for years and, at first, whenever I had this, I had to get the LG Mobile Tool plus the full factory ROM to do a KDZ restore -- i.e., start everything from scratch.
There's zero need to do that -- if you had a working TWRP recovery and Android system before, both will still be fully functional after you overcome this problem!
First: you have to get back into TWRP.
This is the hardest part because not only the key press sequence is rather uncommon, you have very little time to get through it, too.
In short, you have to press VOL DOWN + POWER keys until you get the LG logo.
Then you have to quickly release and press all three keys (VOL DOWN + VOL UP + POWER), before the "Secure Boot" error message comes up.
Second: What comes up doesn't make a lot of sense, too: you're dropped in the "Factory Reset" screen.
You'll have to press POWER twice to confirm -- never mind the dire warnings -- to get back into TWRP.
Try again if you don't succeed or check the YouTube video pointed above by HerrRuin good to see how it's done.
Third: once in TWRP, it gets easy.
Download the bumped bootloader from AndroidFileHost, also pointed by HerrRuin above.
(FTR, file name is 'v500-loki-kernel-to-bumped-kernel-signed.zip'; MD5 is 'f1a25de31559462d8c5d4c35d23f84d9')
While still in TWRP, connect the tablet to your computer and transfer the file over.
After the file is copied, flash it via the "INSTALL" button, reboot, and "Bob is your uncle"... :laugh:
Many thanks to everyone who contributed to this solution that allows me to keep enjoying my G Pad after so many years.
SOLVED!
So, after just giving up and moving on to another project of trying to flash the ARTX Kernel which didn't work (I'll update this if I find out why it's not working; my phone restarts when im flashing the zip and "2013-2015 [somename ] amurlle.com" pops up in log.) so I researched and found a zip called MrBump.zip which bumps your boot image to get rid of the secure boot check.
How to
Flash SuperSu v2.82.zip via TWRP and then flash MrBump.zip, the phone will reboot after flashing MrBump and then another time for finishing the SuperSu installation.
History
\\
So, I have recently updated from Cyanogenmod 13 to Lineage OS 14.1 as it's faster, pretty, and Xposed was recently released for Nougat.
Installing Lineage wasn't a problem nor Gapps or the su add on package from Lineage which unlocks the OS's own su management service.
I wanted to use SuperSu as it pretty, customization, and better privilege management compared to the option lagging 'Privacy Guard' Lineage uses.
So, I flashed the SuperSu v2.82 zip which gave me a "Secure Boot Error" when rebooting into the system. No partitions seemed to be corrupted or damaged but I assumed
it had to do with the boot.img file as I saw supersu patch the boot image for some stuff I don't know. I decided to research and get my team of arduino super AI's to find
something of an answer of how to fix my problem, stumbling upon an article on XDA from chainfire of a boot image signer. I used Cywgin to create an rsa key and signed my boot image
then figuring out I could use the "BootSigner.zip" to sign the boot image without me creating a rsa key, flashing the zip nothing changed just some other error of where it couldn't read
boot image or the boot image was misdirecting to the system. I then tried fastbooting the signed boot image I made, it didn't work giving me some other ****ty error of mutiny.
I then fastbooted the orginal unsigned boot image I took from my ROM which worked but when booting into the OS SuperSu was still not the active su manager.
I then gave up and am now writing this post in a last option of getting SuperSu on my phone.
I have tried SuperSu 2.78 and kingoroot from the PC hoping that I could then use SuperSuMe
//
Details of my device
\\
LG G3 D855
ARM
Lineage OS 14.1 (20170724)
Gapps 7.1 Micro (20170728)
TWRP 3.1.1-0
//
1 second after turning on the phone the error pops up (the LG logo is visible when the log is onscreen):
ERROR : boot certification verify
[640] --------------------------------------------------
[640]
[640] Secure boot Error!
[640] Cause: boot certification verify
[640]
[640] ---------------------------------------------------
2 seconds later the screen blanks and the LED on my phone blinks blue and red at half second intervals.
Any help would be appreciated, if you need any specifics of my device or screenshots just ask (I can replicate my problems and steps iv'e done if you need me to.)
Eureka!
I did the exact same thing and all the guides that I found assumed that you still had access to the system or had already wiped out download mode. There is a lot of advice out there that really just doesn't work. Anyway, I gave up and decided to do a wipe with suprising results.
boot to stock recovery by holding power+volume down
perform factory reset
phone reboots to TWRP - WHY?!?! I have no idea, but it worked
reinstall your latest lineage image from /data/data/org.lineageos.updater/app_updates/
wipe davlik/cache + reboot
profit!
I don't know why this worked and I stumbled upon this by accident.
Mileage may vary, so please share your results.
XtatX said:
I did the exact same thing and all the guides that I found assumed that you still had access to the system or had already wiped out download mode. There is a lot of advice out there that really just doesn't work. Anyway, I gave up and decided to do a wipe with suprising results.
boot to stock recovery by holding power+volume down
perform factory reset
phone reboots to TWRP - WHY?!?! I have no idea, but it worked
reinstall your latest lineage image from /data/data/org.lineageos.updater/app_updates/
wipe davlik/cache + reboot
profit!
I don't know why this worked and I stumbled upon this by accident.
Mileage may vary, so please share your results.
Click to expand...
Click to collapse
What?
You must've flashed TWRP before, and I don't understand what you mean here. Did you brick your phone trying to flash SuperSu too?
But i'm glad it worked out for you
Bump!
Saterlite said:
What?
You must've flashed TWRP before, and I don't understand what you mean here. Did you brick your phone trying to flash SuperSu too?
But i'm glad it worked out for you
Click to expand...
Click to collapse
Yeah, I had TWRP on it before and got to that point by trying to flash SuperSU on an already installed copy of Lineage. I was really trying to revert to stock and start over when TWRP came up.