So a couple of months ago, I installed the official, yet korean, firmware (Android Version 5.0.2) on my Lg G Pad V500.
Now I wan´t to install Lineage OS but I always fail to install TWRP.
I followed this guide and also tried the guide from lienage os. I flashed the proper TWRP version with the official TWRP App and the app claimed that it was successfully.
Here comes the problem:
I can´t boot into recovery mode.
I tried it with adb "adb reboot recovery" but ended up by the LG Logo and a message in the upper left corner telling:
secure booting error! cause: boot certification verify
Click to expand...
Click to collapse
I also tried the key combination while booting (POWER + volUP + volDOWN) but that didn´t work either.
Here are some Specs:
Android version: 5.0.2
Kernel version: 3.4.0
Build Number: LRX22G
Software version: V50030a
Which TWRP Version did you use? I have a v500 too and was running fine with twrp 3.2.2.0. I yesterday updated to twrp 3.2.3.0 and get the same error while trying to boot into twrp. I guess 3.2.3.0 is the problem.
I'm also getting that since latest updates... Spent 3 hours trying to boot into recovery only managed it once and clearing cache didn't fix it. Haven't been able to get in again...
Tried with TWRP 3.2.2-0
meistadieb said:
Which TWRP Version did you use? I have a v500 too and was running fine with twrp 3.2.2.0. I yesterday updated to twrp 3.2.3.0 and get the same error while trying to boot into twrp. I guess 3.2.3.0 is the problem.
Click to expand...
Click to collapse
I tried version 3.2.2-0 but go the same message when trying to reset.
Which rooting method did you use? I bought mine v500 used and twrp was already installed, so I hadn't to deal with rooting and all that stuff. I recently read a lot about and think I will have to try different method to get twrp running again. But if you have hints for me, I would be thankfull.
I vaguely remember that you had to use 4.4 kitkat base for root & TWRP, not 5.x. Don't know if this still apply.
meistadieb said:
Which rooting method did you use? I bought mine v500 used and twrp was already installed, so I hadn't to deal with rooting and all that stuff. I recently read a lot about and think I will have to try different method to get twrp running again. But if you have hints for me, I would be thankfull.
Click to expand...
Click to collapse
I used KingoRoot
Related
Hi,
Phone Model: D855
Software Version: Lollipop
TWRP Version: 2.8.7.0
I was looking for a solution and all I found are solutions for bricked phones which is not my case.
I tried flashing via Flashify the "TWRP" recovery.
When i rebooted into recovery from Flashify or Quickboot it says "secure booting error" or what ever and gets into a bootloop - which ends when i just take the battery out.
What should I do to use the recovery?
Thank you!
Downgrade to KitKat and then install TWRP
Use autorec for d855 /available in playstore/. Should work fine on LP. After flashing successfully update to 2.8.7.0 via recovery.
First of all, I had a LG G3 (D855) with cyanogenmod 13 on it.
Since my twrp didn't work and i had a pretty old cm13 version on my G3, I wanted to flash twrp again and I used the AutoRec apk from this post (http://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268), because I couldn't flash anything in my old twrp.
After flashing the new twrp, my G3 could only boot into the twrp recovery, so I searched for a solution and fount this post: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
I did everything like the guy said in the post and it didn't work, so I used the last command in his post. After trying to boot into sytem it didn't work, but this time I got into the "cyanogenmod recovery" in which im stuck now.
So the first thing I did in cm recovery was looking for the possibility to flash an image, which just isn't there. So I tried flashing the newest cm13 nightly through the "Apply update" option in the cm recovery, which didn't work because I needed Baseband version 21C.
After that I obviously tried to flash Baseband 21C, which again didn't work, because the footer is wrong.
So I surfed through the internet, when I had to notice, that ADB (and fastboot) doesn't work in cyanogenmod.
Now I'm stuck here with this ****ty cyanogenmod recovery, where I can do nothing.
I hope that anyone of you can help me with this problem
Can't you go back to stock with a KDZ flash? Just boot into download mode.
A similar thing happened to me, but it was a TWRP boot loop. I tried the LGUP flash of a .kdz file, but that failed, so then I tried an earlier version of Android using LG Flash Tool 2014 and it was fine after that. Then I just updated to latest stock Android and rooted with Kingroot. Can you at least boot into download mode? (power off while not connected to PC, then press vol up I think at the same time as plug in USB cable).
Edit:
I installed some LG Drivers from a root article and now the phone is recognized. I can update to V20G and test it again, hope it works!
Hello!
I was running CM14.1 on my LG G4 and a few days ago I decided to install a new update but from within the phone itself. Sadly, it just rebooted to the recovery and didn't install anything. And from there, it always rebooted into the recovery no matter what I did. I also did a full wipe and installed CM14.1 clean but it still rebooted to the recovery and didn't want to go past that. I made a Reddid thread - https://www.reddit.com/r/cyanogenmod/comments/5gcap3/g4_h815_cm_141_help_i_cant_boot_outside_of/.
So I got help with that - I got into Download Mode and flashed the stock software via LGUP. Sadly, after I did this, I can no longer install a custom recovery. The phone is not rooted and LGUP and LG Bridge don't recognize the device anymore and the phone says there isn't a new update available but it's on the 5.1 stock ROM.
Whenever I flash the TWRP image via fastboot and I reboot into recovery, it doesn't boot into TWRP but it boots into some kind of other fastboot mode. And I've tried to issue `fastboot boot twrp-x-x-x.img` but it fails to do so and shows `FAILED (remote: dtb not found)`.
Is there a way to fix this so I can flash CM again?
Thanks in advance!
Peshyy said:
Hello!
I was running CM14.1 on my LG G4 and a few days ago I decided to install a new update but from within the phone itself. Sadly, it just rebooted to the recovery and didn't install anything. And from there, it always rebooted into the recovery no matter what I did. I also did a full wipe and installed CM14.1 clean but it still rebooted to the recovery and didn't want to go past that. I made a Reddid thread - https://www.reddit.com/r/cyanogenmod/comments/5gcap3/g4_h815_cm_141_help_i_cant_boot_outside_of/.
So I got help with that - I got into Download Mode and flashed the stock software via LGUP. Sadly, after I did this, I can no longer install a custom recovery. The phone is not rooted and LGUP and LG Bridge don't recognize the device anymore and the phone says there isn't a new update available but it's on the 5.1 stock ROM.
Whenever I flash the TWRP image via fastboot and I reboot into recovery, it doesn't boot into TWRP but it boots into some kind of other fastboot mode. And I've tried to issue `fastboot boot twrp-x-x-x.img` but it fails to do so and shows `FAILED (remote: dtb not found)`.
Is there a way to fix this so I can flash CM again?
Thanks in advance!
Click to expand...
Click to collapse
The bootloop to recovery is a known issue of one the December nightlies of CM 14. Head over to the CM thread and search for bootloop and twrp. They provided a solution to solve this too.
Besides that: which twrp version do you tried to fastboot? H811 or h815? Taken from the official download site?
.
steadfasterX said:
The bootloop to recovery is a known issue of one the December nightlies of CM 14. Head over to the CM thread and search for bootloop and twrp. They provided a solution to solve this too.
Besides that: which twrp version do you tried to fastboot? H811 or h815? Taken from the official download site?
.
Click to expand...
Click to collapse
twrp-3.0.2-1-h815.img, H815 as the title says and from the official website as I've always done. As for the thread - I don't have TWRP and I can't even flash it as I've written in my post. That's what I'm struggling with.
Edit:
I installed some LG Drivers from a root article and now the phone is recognized. I can update to V20G and test it again, hope it works!
When I've succesfully installed twrp 3.2.1 or 3.1.1, the phone stuck in boot logo while recovery mode loading and than reboot again. But when I've installed twrp 3.0.2 there is no problem on entering twrp menu. Version 3.2.1 and 3.1.1 does not compatible with Z551ML?
I'm using Android 5 (Lolipop) by the way...
Found the problem. 3.1.1 and upper versions works with only android 6 bootloader. I've another question than... Is there any way to retun original recovery mode from TWRP?
I've upgraded my phone to android 6 and than flash twrp 3.2.1 again but I got same result.
rangerofsoul said:
I've upgraded my phone to android 6 and than flash twrp 3.2.1 again but I got same result.
Click to expand...
Click to collapse
where you find 3.2.1? you sure its for zenfone2? if yes then 3.2.1 support android 8.1
you need test loower versions
zentao78 said:
where you find 3.2.1? you sure its for zenfone2? if yes then 3.2.1 support android 8.1
you need test loower versions
Click to expand...
Click to collapse
I tried 3.0.2 and install lineage OS its succesfully completed. Is there any way to disable "os validation error" on while first boot screen?
zentao78 said:
where you find 3.2.1? you sure its for zenfone2? if yes then 3.2.1 support android 8.1
you need test loower versions
Click to expand...
Click to collapse
It is available on Twrp's official website, and I have it on my z551ml. It is works fine with lineage 14.1.
[HELP] Get stuck in bootanimation &then only boot to TWRP after upgrade Magisk & TWRP
I have sucessfully rooted my phone but yesterday when i upgraded Magisk from 16.4 to 17.1 and then flashed lasted TWRP, my phone some how corrupted .
After that I tried to flash Factory Image and boot TWRP portable -> Flash ElementalX 2.05 -> Magisk 17.1 -> VerifiedBootSigner-v8 -> Reboot but my phone get stuck in bootanimation about 5 min and then reboot to recovery. Then it will always boot back to recovery when I reboot.
I have searched here but couldn't find any solution.
I tried to flash ElementalX and TWRP only and my phone booting normally. But anytime I flash Magisk it can't.
Please help me, I don't know what to do next, Thank you and sorry for my bad English. :crying:
I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.
Cozmikk said:
I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.
Click to expand...
Click to collapse
What version of TWRP did you use?