Hello good folks of XDA, I have run into some problems with my Honor 8, and I am hoping for an advice.
My bootloader is unlocked, I was happily running LineageOS Beta 5 from OpenKirin - I had TWRP 3.2.1. Everything was working fine.
The problems arrived when I tried to flash SuperSU through TWRP. Since then I am stuck in a bootloop. I can access TWRP - although, it is acting out and doesn´t appear to be working properly.
I can access fastboot - I have tried to reflash the LineageOS through fastboot - didnt resolve the bootloop. I then tried to flash OMNI ROM from OpenKirin - still stuck in the bootloop.
Do you guys have any advice on how to recover the phone? eRecovery through wifi fails everytime.
Thank you very much.
Related
Good Afternoon!
Here's the story:
I encrypted my phone.
I installed TWRP 2.8.6.1 Official.
I (tried) unsuccessfully to dirty-flash a ROM to fix a systems partition problem.
My phone gave me an encryption error and told me to format my phone.
I formatted my phone using TWRP and installed OxygenOS again.
My phone is now bootlooping into TWRP.
I've tried downloading OxygenOS again.
I tried formatting my phone again.
I tried a different OxygenOS Rom.
I tried CyanogenMod 12 Nightly.
Everything bootloops back to recovery.
I'm currently trying to find a Factory Image for the O+O and go back to CyanogenMod 11S to (try) and get it to just boot.
Is there anything I haven't tried? Any advice?
Thanks.
I flashed 11S via fastboot and then upgraded to a version of Cyanogenmod12.1 I found via the forums.
The stock CyanogenMod kept getting stuck in the middle. OxygenOS won't install, period.
My phone hates me.
Hey guys,
Got a weird problem with my OPO on a last week. With no reason my phone got a bootloop after a regulair reboot. Nothing special was installed and i can see no reason for such behavior.
I tried to reflash it and so on, but that's there the weirdness starts.
I can install CM11S and CWM of Philz recovery, but any attempts to install TWRP (6.0/6.1/7.0) fails (vol. down + power just leads to reboot). Same for the latest CM12.1 builds. Tried installing those by using several toolkits and flashing via fastboot+cmd. No success. Bootloader was unlocked and seem to be still unlocked. Tried wiping system/data/cache via CWM/Philz - still no chance to get TWRP and CM12.1 work (results in a bootloop).
Anyone experienced such problem, or any ideas on how to solve the problem?
Any help appreciated.
Hey dont know much but it might be a modem firmware issue. Flash the latest cm12.1 modem file and then try installing cm12.1. Generally when i get stuck in bootloop i use the mac osx toolkit to boot the phone into twrp recovery via fastboot mode. But cknsidering you have already tried that then modem issue had given me bootloop once when i had upgraded from 11 to 12.1
Hi all
I decided to try RR 5.8.5 on my wife's old 1st-gen MotoG this evening. so I downloaded RR from https://forum.xda-developers.com/moto-g/development/rom-resurrection-remix-5-8-3-t3590536,
visited twrp.me and downloaded the latest TWRP for the Moto G (2013, Falcon).
The bootloader on this device is unlocked from previous fiddling I did so I simply booted into fastboot mode, flashed the recovery and then booted into TWRP as normal. I then flashed the RR, GAPPS along with Magisk v14 and proceeded to reboot.
The device then proceeded to bootloop so I tried entering recovery only to discover it kept looping back to the boot screen as well.
So I seem to be stuck with no ability to boot the OS or enter Recovery but Fastboot works fine. I tried reflashing the recovery but no dice.
Anyone have any ideas?
Hmmmmm, okay, so after reflashing recovery about 10 times I managed to get back in to TWRP. Going to try wiping and flashing just RR and GAPPS, since it seems this RR rom includes Magisk anyway...
Okay, disaster averted. It seems that installing Magisk v14.0 over Magisk v14.5 (which came bundled into the ROM) caused a minor explosion
hello
I have unlocked the Oneplus 7 Pro and installed twrp .
Have already had several roms installed and tried.
Wanted to try this morning the Rom Havoc-OS-v3.12-20201219-guacamole-Official-GApps.
Installed that and then twrp again.
Now I am in bootloop, I can not get into recovery. The TWRP logo appears briefly then reboot.
I can't get into the Fastboot either.
Is there still a solution ?
Thanks
Sgiro said:
hello
I have unlocked the Oneplus 7 Pro and installed twrp .
Have already had several roms installed and tried.
Wanted to try this morning the Rom Havoc-OS-v3.12-20201219-guacamole-Official-GApps.
Installed that and then twrp again.
Now I am in bootloop, I can not get into recovery. The TWRP logo appears briefly then reboot.
I can't get into the Fastboot either.
Is there still a solution ?
Thanks
Click to expand...
Click to collapse
hey check this yt video and follow his instructions make sure to flash oos on both slots
Dear Community,
I hope someone can help me with my problem.
My Oneplus 5 (cheeseburger) is running Android 11 (/e/ OS from e foundation, based on LineageOS for microG, rooted with Magisk). My recovery until yesterday was TWRP 3.6.2_9-0. The whole system ran great, no problems.
Then yesterday I updated TWRP to the latest version 3.7.0_12-0. To do this I booted into the recovery and flashed the .img file there, as I always did. But when I booted into recovery again right after that, my unlock pattern didn't work anymore. Then I booted into the OS; the unlock pattern worked, but I can no longer get into the system settings and Bluetooth won't turn on. However, the apps all seem to work normally.
I then flashed TWRP 3.6.2_9-0 in fastboot mode via adb. Now the unlock pattern in TWRP worked. I then flashed the /e/ OS rom again. But that did nothing, I still can not get into the system settings and Bluetooth does not work.
Now I have two questions:
1. how can it be that updating TWRP leads to such problems?
2. what did I do wrong?
Thanks a lot for your help!
Can no one really explain to me how this problem came about?
I have now installed Android 12 cleanly, TWRP is 3.7.0_12-0.
What do I do when a new TWRP update comes? I don't even dare to install it if it then shatters my operating system again.