So I've recently started modding my htc one m8 and I suddenly can't access twrp recovery. I choose recovery from the bootloader menu, it shows the loading screen with the teamwin logo, then the screen goes black and reboots normally. I have an unlocked bootloader, the crdroid nougat rom installed and I have magisk installed as well. I've tried flashing twrp again with no luck. Any tips?
edit: nvm it was out of battery
Related
Hello @xda
I ran into some ussues lately with TWRP and M5 kernel made by @Myself5
Until last week I have been using M5-kernel with Validus ROM, and it has all been running smooth. I have been able to open TWRP during boot with volume keys and all was joy. Then I decided to try MultiROM and I got that working with the app.
This monday I decided to get rid of it and cleaned my phone.
Then the issues started. I replaced MultiROM TWRP with TWRP and flashed boot.img from validus zip. No problems entering recovery and I successfully flashed the zip and gapps for it. I used his latest version with M5 included. Booting into the ROM was not a issue and it all worked fine until I was trying to get into TWRP.
As I always do before I backup my phone, I shut it down. Then I booted it and tried to enter recovery, the purple light came on, but nothing happened when pressing any keys...
To enter the recovery i had to boot the ROM and reboot to recovery, witch I did not have to do before. I tried all possible solutions, in the end I decided to try with the kernel from a earlier Validus version, and guess what, it opened TWRP.
Is there someone that can tell me WTH I'm doing wrong??
I always do a
<fastboot flash recovery twrp.img and <fastboot flash boot boot.img
After downgrading from Android 5.1 (due to the overheating and battery drain issues) to Android 4.4 for HTC One (M8), I tried flashing the TWRP recovery (twrp-2.7.0.2-m8) and when I boot into the bootloader and select RECOVERY from the list, it just simply loads a black screen with a white Google logo. It just stays like this. One build of TWRP worked, but it was glitchy and there was no button to start mounting over USB.
Any help would be appreciated, thanks!
What hboot? Some TWRP builds don't play well with outdated hboots.
my device is s-off & UNLOCK Htc m9 sprint marshmallow 3.41.651.4 .. after flashing twrp and super su its continiously restarting...i wiped deviac case & case data,changed twrp nothing is working..i used 3.2.2.0 and few older twrp too... can anyone help me in this situation
I successfully flashed TWRP 3.4.0.0 and flashed patched image using magisk, the phone was successfully rooted and I used it as well.
I downloaded SUPER SU apk but showed up "SU binary occupied" so I downloaded an older version that asked me to flash it using either TWRP or without TWRP, firstly I chose without but it failed, so when I chose with TWRP the phone rebooted and still stuck on realme logo!
Tried many solutions but failed, so I hope anybody could help me.
NOTE: realme logo stays for about 70 seconds then it turns into FastBoot mode automatically.
*Tried this one
https://forum.xda-developers.com/2015-moto-g/help/problem-boot-flashing-supersu-t3507127
But in vain
Hello.
I have problem with my Nexus 6P.
Recently it restarted itself and shows only information that the bootloader is unlocked and the Google logo, then it turns off and so on. I have access to the bootloader, but when I try to start recovery, the phone loops. I flashed special twrp on 4 cores and modified boot.img but still to no avail
Karol Trawa said:
Hello.
I have problem with my Nexus 6P.
Recently it restarted itself and shows only information that the bootloader is unlocked and the Google logo, then it turns off and so on. I have access to the bootloader, but when I try to start recovery, the phone loops. I flashed special twrp on 4 cores and modified boot.img but still to no avail
Click to expand...
Click to collapse
Try flashing the TWRP and workaround.zip in this thread.
https://forum.xda-developers.com/t/...-death-blod-workaround-flashable-zip.3819515/