[Q] Secure booting error : Boot certification verify in recovery mode - G Pad 8.3 Q&A, Help & Troubleshooting

Hello !
I installed the 5.1.1 AOSP rom to update my 5.0 rom (AOSP too) by my TWRP recovery. I wanted to next flash SuperSU, but when i try to enter in recovery mode, i got this : "Secure booting error : Boot certification verify". I tried to reinstall the recovery, but i need to be rooted, and for being rooted, i need to flash SuperSU, so i'm stuck.
I can use my tablet perfectly, but i can't get to the recovery.
Thank you for your help !

What variant of the the G Pad 8.3 are you using? VK810, V500, V510? You HAVE to find out how to root first because without root, you can't flash a custom recovery. I only know rooting details for the VK810 and I'm guessing you have the V510 (GPE - Google Play Edition) since you say you're on AOSP already. I'm sure if it's rootable there's a thread in these sections about it for your variant. When a device is rootable, there's always an initial way to get there without flashing SuperSU, except possibly for Samsung when you can flash ODIN-compatible repackaged custom recoveries.

I forgot to put it but i have a V500, i didn't had this problem when i installed 5.0 AOSP (firstly i had the LG stock ROM).
I saw that i can install TWRP with ADB, but it is for the GPE only :/

If you already had TWRP flashed then you've got some other problem going on. Maybe you have to downgrade the bootloader (aboot.img) in order to get into custom recovery on the V500? We do on the VK810. If that's the case then that means that somehow you had updated your bootloader since the last time you got into TWRP.
You might end up having to go back to square one, put whatever stock ROM on it that allows you to root it and install TWRP, ensure you can get into TWRP and the ROM fine, then flash whatever ROM you want. If the ROM you want doesn't already have root capability baked in, such as current CyanogenMod builds do, then make sure and flash SuperSU from TWRP before you exit out of custom recovery.

Related

New to rooted LG GPad-have questions

Hi folks. Long time rooter/rom user of phones and tablets. I have some questions for my V500
Since it is rooted, would this be the next step - http://forum.xda-developers.com/showthread.php?t=2641409
(Installing TWRP for a custom recovery)
Since I'm on 4.4.2 with a V50020d base, would I then focus on getting 4.4.2 base roms and flash them via that TWRP I installed?
This does seem like a really fun and snappy device. From what I can tell, it has an IR Blaster right? Are there any roms that don't work with the blaster (I see this sometimes in the Galaxy Tab roms for devices that have the IR blaster)
Once you root, the next step is installing TWRP so you can install roms.
I also have the V50020d UK version.
Stumproot which is available here worked fine for me, easiest root i have ever done. Just install apk and your done.
Installing and getting custom recovery to successfully flash a ROM is another story. I have managed to get TWRP flashed to the device and boots correctly. However it fails when i try to flash CM11 or any other ROM. After reading around I think I may have to downgrade the stock 4.4.2 to 4.2.2 in order to get TWRP to flash. I am not struggling to find the correct stock 4.2.2 kdz firmware for the v50020d device.
It's been a bit of a head scratcher! Let me know how you get on with yours.
Cracked it today. I've written a guide for all UK users who are stuck with V50020d, compiling all the info. http://forum.xda-developers.com/lg-g-pad-83/help/v50020d-uk-root-twrp-flash-stock-4-4-2-t2938914
Hope it helps
fresh87 said:
I also have the V50020d UK version.
Stumproot which is available here worked fine for me, easiest root i have ever done. Just install apk and your done.
Installing and getting custom recovery to successfully flash a ROM is another story. I have managed to get TWRP flashed to the device and boots correctly. However it fails when i try to flash CM11 or any other ROM. After reading around I think I may have to downgrade the stock 4.4.2 to 4.2.2 in order to get TWRP to flash. I am not struggling to find the correct stock 4.2.2 kdz firmware for the v50020d device.
It's been a bit of a head scratcher! Let me know how you get on with yours.
Click to expand...
Click to collapse
I did mine with towelroot. I'll be looking to flash a custom recovery soon. I wanted to pop in here first to double check before going ahead with a recovery and a rom.
I new to LG and have 2 of these for my boys.
I have a us and uk one, i assume these will need different ways of rooting and flashing twrp etc?
I rooted one with Kingoroot no issues, but damn, getting cwm to install is a mare.
Both mine are on 4.4.2.
Looked at so many tuts, they all change due to time and i had to give up as was draining me.
Any tips on how to get cwm installed fella.
Best wishes
I've just created a tutorial for first time custom recovery installation.
http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-t2945917
Deltadroid said:
I've just created a tutorial for first time custom recovery installation.
http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-t2945917
Click to expand...
Click to collapse
Thank you Delta. I will check it out ASAP.

[Q] STuck at boot logo. Want to flash stock but don't know firmware

Hi I need help. I recently got this phone.
Rooted it with stump root, and flashed TWRP 2.8.4 using flashify.
I tried to flash a custom rom, but the wiping data part had an error. Stupidly enough, I proceeded to flash the rom zip and it got stuck flashing so I had to power it off. Now my phone is stuck on the boot logo. The only thing I can do with it is turn it off, or enter download mode. But I can't enter recovery mode. I read somewhere that it is possible to go back to stock recovery using the flashtool. Problem is I don't know which firmware I have. The only information I had about the firmware was that it was ls980vze because that's what I saw when I was flashing something. How do I deal with this? :crying:
p/s if there's a way that I can access twrp, maybe that' would work because I made a nandroid backup before. Don't know if that's useful though.
zach_95 said:
Hi I need help. I recently got this phone.
Rooted it with stump root, and flashed TWRP 2.8.4 using flashify.
I tried to flash a custom rom, but the wiping data part had an error. Stupidly enough, I proceeded to flash the rom zip and it got stuck flashing so I had to power it off. Now my phone is stuck on the boot logo. The only thing I can do with it is turn it off, or enter download mode. But I can't enter recovery mode. I read somewhere that it is possible to go back to stock recovery using the flashtool. Problem is I don't know which firmware I have. The only information I had about the firmware was that it was ls980vze because that's what I saw when I was flashing something. How do I deal with this? :crying:
p/s if there's a way that I can access twrp, maybe that' would work because I made a nandroid backup before. Don't know if that's useful though.
Click to expand...
Click to collapse
Okay, quick and easy.
There is a zve tot, though before we do much. Custom ROM as in which one?
Anything CM based is radio zv8, if it is a cloudyfa ROM; you can be zva to zve radio.
So depending on which can save trouble.
Root, depends on which version you are. Zv8 - go with ioroot25. Zve - use stump root.
Next thing, forget flashify. Sometimes it works sometimes it doesn't. Tried and true method, Auto-rec. Only after root.
Upgrade TWRP through TWRP by gator's zip of bumped and such. Or use TWRP app.
Again if your zv8, flash your CM based ROM of choice.
Zva-zve, flash your stock based like cloudyfa's Roms and such.
secret.animal said:
Okay, quick and easy.
There is a zve tot, though before we do much. Custom ROM as in which one?
Anything CM based is radio zv8, if it is a cloudyfa ROM; you can be zva to zve radio.
So depending on which can save trouble.
Root, depends on which version you are. Zv8 - go with ioroot25. Zve - use stump root.
Next thing, forget flashify. Sometimes it works sometimes it doesn't. Tried and true method, Auto-rec. Only after root.
Upgrade TWRP through TWRP by gator's zip of bumped and such. Or use TWRP app.
Again if your zv8, flash your CM based ROM of choice.
Zva-zve, flash your stock based like cloudyfa's Roms and such.
Click to expand...
Click to collapse
I tried to flash Validus ROM so i'm guessing that's zv8? I am rooted btw. Wait so you can upgrade twrp by flashing another twrp file? When I used flashify, after flashing the 2.8.4 bumped twrp it rebooted to my current twrp 2.7.0 and flashed it so I thought it was just the same. I'm pretty sure I am zve. Can I flash a zv8 rom if I have a zve rom? How do I get out from the bootloop?
zach_95 said:
I tried to flash Validus ROM so i'm guessing that's zv8? I am rooted btw. Wait so you can upgrade twrp by flashing another twrp file? When I used flashify, after flashing the 2.8.4 bumped twrp it rebooted to my current twrp 2.7.0 and flashed it so I thought it was just the same. I'm pretty sure I am zve. Can I flash a zv8 rom if I have a zve rom? How do I get out from the bootloop?
Click to expand...
Click to collapse
Basically you're stuck using the ZVE tot to bring it back to factory. Be sure to boot it at least once as the phone will have to re-activate itself.
Try the zv8 modem
http://forum.xda-developers.com/showthread.php?t=2451426
And if not, then try you and always check the op carefully before flashing.

[Q] A few questions about Custom ROMs

Hello everyone! I'm not really new to this Android rooting and unlocking bootloader stuff (I did this to my previous Xperia phones) but I'm "new" with it now because I'm now an LG user. I currently own the D855 Global variant.
So here are my questions:
1.) Is it necessary to unlock the bootloader to flash custom ROMs? Or is root enough? (I rooted my phone yesterday and installed TWRP with AutoRec for D855 users) I'm kinda interested with the Cloudy G3 ROM.
2.) Is it necessary to unlock the bootloader to flash custom kernels?
3.) What does bump mean? I haven't heard this term before.
1) No, you do not need to unlock your bootloader on lg g3 to flash Cloudy ROM or other custom ROMs.
You are not even able to unlock the bootloader on this phone currently. If you already
flashed TWRP go get your Cloudy ROM and flash it with TWRP.
2) Again no. Like I said you are not able to unlock bootloader on this phone currently.
But you will be able to flash custom kernels because they are BUMPed.
3) And finally BUMP is a way of signing boot image so it could be booted on LG bootlader without the bootloader itself being unlocked. All XDA ROMS for LG G3 I found here are already prebumped so you are able to download them and flash immediately.
NatusVincere said:
1) No, you do not need to unlock your bootloader on lg g3 to flash Cloudy ROM or other custom ROMs.
You are not even able to unlock the bootloader on this phone currently. If you already
flashed TWRP go get your Cloudy ROM and flash it with TWRP.
2) Again no. Like I said you are not able to unlock bootloader on this phone currently.
But you will be able to flash custom kernels because they are BUMPed.
3) And finally BUMP is a way of signing boot image so it could be booted on LG bootlader without the bootloader itself being unlocked. All XDA ROMS for LG G3 I found here are already prebumped so you are able to download them and flash immediately.
Click to expand...
Click to collapse
Thank you so much! Another question tho, if I flash any stock based custom kernel, how do I get back to stock if in any case I would want to?
Before flashing anything you should always do backup with TWRP or other custom recovery you already have. If you did your backup there, just restore it that way.
In case you did not, you are able to use LG flash tool and flash stock kdz files.
Also you could backup your boot.img(kernel that is...) using app like Flashify and restore it with it if necessary.
And again I recommend doing a nandroid backup with TWRP before flashing anything at all.

Root

How do I root my tmobile m8 running Android 5.0.1 and bootloader unlock. Also custom recovery so I can flash a 6.0 ROM
You're saying your bootloader is already unlocked? It may already have custom recovery installed. Just pick "recovery" from bootloader, and see if TWRP boots.
If not, just flash TWRP with fastboot.
You don't need to root, if you are going to go and flash a custom ROM anyway. Depending on the ROM, it may already be rooted. Otherwise, flash the appropriate SuperSU version.
redpoint73 said:
You're saying your bootloader is already unlocked? It may already have custom recovery installed. Just pick "recovery" from bootloader, and see if TWRP boots.
If not, just flash TWRP with fastboot.
You don't need to root, if you are going to go and flash a custom ROM anyway. Depending on the ROM, it may already be rooted. Otherwise, flash the appropriate SuperSU version.
Click to expand...
Click to collapse
No its not unlocked, I want to unlock it. And can I go from stock 5.0.1 to a custom 6.0 ROM?
I got everything situated thanks
NexusS4gFreak said:
No its not unlocked, I want to unlock it. And can I go from stock 5.0.1 to a custom 6.0 ROM?
Click to expand...
Click to collapse
I know you got it sorted out. But its best to post your solution, for the benefit of others that my have the same issue/questions and be looking at the thread in the future:
For a completely stock device on Lollipop, the suggested sequence to install a custom ROM:
1) Unlock the bootloader by HTCDev.com (the process is rather self-explanatory if you follow the instructions on the website)
2) Install custom recovery TWRP 2.8.7.0 by fastboot
3) Flash the MM ROM of your choice. Most will work with Lollipop firmware (meaning, if your phone was on LP when you were stock) but check the thread of the particular desired ROM to be sure.
4) Most ROMs are pre-rooted. But again, check the desired ROM thread to confirm (as root on MM is a little different from past builds).

Is it possible to install TWRP on D850 stock Marshmallow?

Hi, I am trying to flash TWRP on my AT&T stock D850. I have a temporary root using Kingroot, and then I tried flashing TWRP from Flashify, but when I try to enter recovery it says SIG_LEN_MISMATCH: boot verification failed. Normal booting works fine.
A lot of the methods that involve 'bumping' the TWRP img etc., seem to be geared towards Lollipop. Has anyone been able to successfully install a custom recovery while on stock MM and using Kingroot root?

Categories

Resources