I got cm 13 running on my d801 g2 the other day and I'm not a fan of it so I'm planning on flashing to cloudy g2 2.2 but now i am unable to boot into twrp. I enabled root, installed twrp and even enabled advanced reboot to boot directly into recovery but i keep getting secure booting error Cause: boot certification error which is what i was getting on stock android before getting cm13, i fixed the issue before with the kitkat auto rec app but ive read that auto rec can cause a hard brick if used in marshmallow. Trying to get into twrp through twrp, cm advanced reboot, hard key(power and vol down) recovery, flashify and adb reboot recovery command all cause the same error message. Any advice? I tried flashing twrp 3.0.0.4 and that put me into fastboot as does any other twrp version I've tried in flashify.
Related
Hi all,
I'm trying to get root access on my OPO, so I read some information about the process.
It has CM 11S R38.
* Update recovery unchecked.
* Bootloader unlocked.
Til here everything is OK. The problem starts when I install TWRP or any other custom recovery (I've tried also with Philz CWM). After the installation (via fastboot) it says everything was correct, but when I restart in Recovery the device just "freezes" (actually is the screen which keeps with OPO Logo) and then it becomes to black screen. After this happens I have to force a soft-reset to restart system.
I've tried to roll back to the stock recovery and it works perfectly. But any time I try to flash the custom recovery again, then blackscreen...
I really want to root my device, but I need the custom recovery to install the binaries.
I would be happy if I can bypass the recovery installation, that's not compulsory for me. My plan was indeed flash the binaries and roll back to stock recovery.
Thanks in advance!:good:
ironwick said:
Hi all,
I'm trying to get root access on my OPO, so I read some information about the process.
It has CM 11S R38.
* Update recovery unchecked.
* Bootloader unlocked.
Til here everything is OK. The problem starts when I install TWRP or any other custom recovery (I've tried also with Philz CWM). After the installation (via fastboot) it says everything was correct, but when I restart in Recovery the device just "freezes" (actually is the screen which keeps with OPO Logo) and then it becomes to black screen. After this happens I have to force a soft-reset to restart system.
I've tried to roll back to the stock recovery and it works perfectly. But any time I try to flash the custom recovery again, then blackscreen...
I really want to root my device, but I need the custom recovery to install the binaries.
I would be happy if I can bypass the recovery installation, that's not compulsory for me. My plan was indeed flash the binaries and roll back to stock recovery.
Thanks in advance!:good:
Click to expand...
Click to collapse
i had issue when my recovery was always returned to stock CM recovery
- in developer options there is checkbox "Update CM recovery", have you unchecked that?
Night5talker said:
i had issue when my recovery was always returned to stock CM recovery
- in developer options there is checkbox "Update CM recovery", have you unchecked that?
Click to expand...
Click to collapse
Yes, and did not work.
But finally I managed to install Philz Recovery. So it's solved for me. :good:
I have the same problem, but I need multirom and without TWRP it doesn't work. Anyone help us?
ValoXis said:
I have the same problem, but I need multirom and without TWRP it doesn't work. Anyone help us?
Click to expand...
Click to collapse
For me TWRP works only on ColorOS but the OS doesn't boot, with 11S the OS boots but recovery doesn't boot.
Hi all,
Recently I updated my Nexus 5 from Lollipop to Marshmallow 6.0.1 (MMB29Q) - latest build.
everything stock works fine but, once I flash a customer recovery, in my case TWRP it stops working...I get either a startup loop or TWRP gets erased by stock recovery.
I tried various steps ...
flashed TWRP 2.8.7.1 - rebooted to boot loader was able to get into TWRP but, once I reboot system, everything works but TWRP is gone/erased and replaced by stock recovery?
Flash TWRP 2.8.7.1, then flash latest TWRP 3.0, reboot to boot loader and can get into TWRP but once i reboot into system, I am stuck on the initial boot loop.
I have to start from scratch of flashing system and boot etc to get past the loop and it still replaces TWRP with stock recovery.
I can always get into Fastboot but when I go to recovery it seems its being replaced by stock recovery.
anyone experiencing this issue? thanks for your help.
I guess I am doing something stupid but, not sure what...and thanks for your help
If you give more detail on the steps you are taking it will be easier for someone to help. Also, have you tried doing a factory reset when it bootloops?
thanks for the response..here are the details..
I had Lollipop with TWRP 2.8.7.1
yesterday, I downloaded latest build from android site...extracted all files....booted into bootloader and flashed all files..
rebooted - Marshmallow works perfectly...offcourse it not rooted yet or its locedback due to this flash
Scenario:1
So downloaded TWRP 2.8.7.1 and flashed it as recovery, no errors nothing...i rebooted to bootloader and went to recovery to confirm TWRP is there
I rebooted the system - TWRP gives option to root which I said yes so its rooted. I reboot system, this goes into bootloop - I wait for say 5-10 min in this loop mode and I see that adb can recognize the device but nothing else....its stuck in loop
when I force shut down by holding power button for few sec - and go back bootloader/recovery - TWRP is still there
***note*** I did factory wipe in TWRP but that did not fix above condition.
Scenario2:
exact same steps but after I flashed twrp2.8.7.1, I rebooted bootloader and flashed twrp 3.0 as well confirmed twrp 3.0 is flashed and rebooted system - phone start normally no issues - when I restart to bootloader - no TWRP exists, its replaced by stock recovery
Scenario 2, I tried couple of other ways and still the same thing happens - twrp 3.0 get erased.
not sure what I am doing wrong but TWRP doesn't stick
since this is my active device - i flash system.img and boot.img to get the phone to working condition
thanks for your help
Try flashing the latest supersu to get root.
audit13 said:
Try flashing the latest supersu to get root.
Click to expand...
Click to collapse
That did the trick.....thank you very much. I was using older version of supersu thinking it was latest.....I downloaded V2.65 and installed it and that fixed all my troubles..
muchas gracias
I flashed the 2016-03-04 nightly build of AICP using TWRP. Everything flashed smoothly, booted into the new rom, looked good. I went to reboot into recovery to flash the gapps and instead of getting TWRP as I expected i got an error that says
Boot certification verify
Secure booting error
Cause: boot certification verify!
If i reboot the phone it will boot into the rom no problem.
I cant flash a previous backup or a different rom since I cannot access recovery. I don't think there is a 6.0 compatible version of Autorec, I have tried using Rom manager and TWRP manager to flash a recovery with no success.
Anyone seen this before or have a solution?
**Edit**
I decided to just flash back to stock and start over. Seemed simpler than finding some kind of workaround.
Harrisdude9 said:
I flashed the 2016-03-04 nightly build of AICP using TWRP. Everything flashed smoothly, booted into the new rom, looked good. I went to reboot into recovery to flash the gapps and instead of getting TWRP as I expected i got an error that says
Boot certification verify
Secure booting error
Cause: boot certification verify!
If i reboot the phone it will boot into the rom no problem.
I cant flash a previous backup or a different rom since I cannot access recovery. I don't think there is a 6.0 compatible version of Autorec, I have tried using Rom manager and TWRP manager to flash a recovery with no success.
Anyone seen this before or have a solution?
**Edit**
I decided to just flash back to stock and start over. Seemed simpler than finding some kind of workaround.
Click to expand...
Click to collapse
did you know the button combo to boot into recovery?
Yeah depending on the recovery or firmware our or something it is either power and volume down. Then power and volume down. Or less commonly power and volume down, then volume down and volume up.
Hi everyone,
I had a big iussue with my phone (Motorola X10T39).
I installed LineageOS 14.1, and I recently updated it at the version 14.1-20180908.
All worked fine, but after the update I lost root privilege.
After that, I updated my TWRP recovery from the version 3.1.0-0 to the version 3.2.3-0, flashing the image(.img) in recovery mode.
The file I flashed was correct, and the phone still boot properly.
But when I turn on the phone in fastboot mode and try to select recovery I get error:
"Invalid boot image size! failed to validate recovery image Boot failed"
What can I do to fix it?
Thanks
silencefalls said:
Hi everyone,
I had a big iussue with my phone (Motorola X10T39).
I installed LineageOS 14.1, and I recently updated it at the version 14.1-20180908.
All worked fine, but after the update I lost root privilege.
After that, I updated my TWRP recovery from the version 3.1.0-0 to the version 3.2.3-0, flashing the image(.img) in recovery mode.
The file I flashed was correct, and the phone still boot properly.
But when I turn on the phone in fastboot mode and try to select recovery I get error:
"Invalid boot image size! failed to validate recovery image Boot failed"
What can I do to fix it?
Thanks
Click to expand...
Click to collapse
Try these steps in order, stopping if a particular works.
- Ensure you installed the correct TWRP image for Peregrine, not for Falcon.
- Try entering fastboot mode manually, if you didn't already try to: Turn off the cell phone, then press and hold the Volume Down button for couple of seconds and while still holding Volume Down button press the Power button for a little bit and then release both buttons at the same time.
- If you updated TWRP with the Official TWRP app, try flashing it manually in fastboot mode: fastboot flash recovery TWRP image name, copied exactly. If you did flash it manually, try installing via the Official app.
- Make sure your downloads for both the Rom and TWRP image are not corrupted - re-download with md5 sum checks and re-flash with verification.
- Backup all your data (including on SD Card) and clean flash TWRP & the rom again (i.e., wipe System, cache, Dalvik cache and format/wipe Data - important).
- If issue persists, re-flash the previous version of the TWRP or rom, depending on which one is the culprit, and report to developer.
silencefalls said:
Hi everyone,
I had a big iussue with my phone (Motorola X10T39).
I installed LineageOS 14.1, and I recently updated it at the version 14.1-20180908.
All worked fine, but after the update I lost root privilege.
After that, I updated my TWRP recovery from the version 3.1.0-0 to the version 3.2.3-0, flashing the image(.img) in recovery mode.
The file I flashed was correct, and the phone still boot properly.
But when I turn on the phone in fastboot mode and try to select recovery I get error:
"Invalid boot image size! failed to validate recovery image Boot failed"
What can I do to fix it?
Thanks
Click to expand...
Click to collapse
This thread is quite old (around 2 years old). But nevertheless, I am sharing my experience so that it may help someone facing similar problem. I have a Moto G 1st Gen Falcon which was running Lineage OS 14.1 based on Android 7.1.2. I was planning to update it to Android 10 based Unofficial Lineage OS. I downloaded latest TWRP zip to update existing TWRP. I rebooted into TWRP and flashed the zip. It installed perfectly. Then to check it attempted to reboot into recovery. But it instead went to fastboot mode with the error "Invalid boot image size! failed to validate recovery image Boot failed". I tried botting into recovery but was not working. I tried flashing through adb a different file but it was not working. Then what worked was booting into recovery using the command Fastboot boot recovery recovery.img. After that I was able to flash Android 10 and now everything is working perfectly.
I unlocked the bootloader through mi unlock tool. I flashed official twrp from their site, 3.3.1-0-violet.img but when I tried booting it into recovery, it got stuck at twrp logo. Then I learnt that it's necessary to wipe userdata using fastboot first so I did that. Then, when twrp started, it was unable to install/wipe/mount any partition. Tried installing magisk using sideload, did work but then device stopped booting.
Figured out a way on how to fix the mount issue, twrp working fine, but then I accidentally wiped /system. Now my device only opens in fastboot, even though I've tried installing, erasing and reinstalling that twrp recovery as well as a couple of others I found in pixel experience forums for my device.
I've got all the stuff needed to install pixel experience, fcrypto disabler, xiaomi latest firmware and the rom itself. Can anyone guide me on how to install it using fastboot?
Also whenever I try booting the recovery image straight from fastboot, it says that command failed, too many links.
I can't boot into recovery via vol up + power button, fastboot doesn't recognize command fastboot reboot recovery.
you need to install stock rom ,then flash twrp but newer unofficial twrp and orangefox twrp boots into recovery even if system partition is empty.
try installing unofficial twrp or orangefox.
orangefox is recommended .