As the title describes, TWRP doesn't seem to be loading anymore and the only change I've made is updating the su binary.
I can get into the fastboot fine, the phone boots fine, but TWRP appears broken. It shows the loading splash, and then just flashes a black screen for a moment, like it's stuck in a loading loop. Device is entirely fine outside of that. I've tried reinstalling TWRP already, had to step down a version, then back up and this problem seems to persist.
To note, I have no clue if updating su caused the problem or if that's relevant, it's just the last major thing I did before this issue came up.
TWRP v3.0.2-0
Issue isn't a bootloop, system is accessible, just the recovery loops.
I have tried fastboot erase cache and it makes no difference, the recovery still just sits there in perpetual loop, unless I need to leave it sitting for longer than 4min.
Fixed, finally.
Downloaded the newest version, 3.0.2-1 and then flashed it directly
fastboot flash recovery twrp-3.0.2-1-victara.img
However my system is no longer bootable, so having to reinstall that.
Related
While attempting to root my device I flashed the recovery successfully with twrp 2.6.1.0 via fastboot terminal on my PC. Device booted to "HTC quietly brilliant" white screen and then does not progress beyond that point. I rebooted into recovery and using TWRP i installed the superuser.zip and it completed successfully. I then reboot again, but does not progress past the "HTC quietly brilliant" white screen (with developer message in red letters at bottom of screen). Device does not progress past this point, I have left for up to 20 min and simply does not proceed.
I am new to the community and probably did some noob mistake, just don't know where. Do I need to flash a ROM? I can reboot into fastboot or recovery, but no OS loads.
I seem to remember seeing here that you need to use 2.5 because 2.6... doesn't work............
flashed TWRP 2.5.0.0 no luck
I re-flashed successfully from 2.6 to 2.5 variant and still same response. I don't have any idea where to go from here.
some success...
odtobe said:
I re-flashed successfully from 2.6 to 2.5 variant and still same response. I don't have any idea where to go from here.
Click to expand...
Click to collapse
Some progress......flashed TWRP 2.5 via fastboot --> sideloaded stock ROM_deodexed 1.31.XXX and was successful at getting phone to boot properly.
Only problem I have noticed at this point is that my gallery keeps crashing when loading my photos, but everything else seems fine. Not a big deal, but when using Zoe mode it saves each frame as a separate photo and can be difficult to navigate efficiently.
I have an HTC One m7 sprint and recently I encountered something usual in the sense that, my battery run out and I placed it on charge while the phone is off. After awhile I try to boot up the device but it takes forever to boot up. I have installed a cm-13 rom on the device which was very stable. I have twrp 3.1.1 installed on the device. my device is S-OFF and bootloader unlocked. For 3 days now I haven't been able to boot up the device to ROM because its always stuck at the cyanogen logo. Whenever i try to boot to recovery, the twrp logo comes and it takes forever to boot into the recovery menu. To be precise, 10-20 mins to boot to recovery menu. Now what buffles me the most is that, I can't format my data because anytime it starts to formatting process starts I get 2 kinds of red line errors:
E: failed to write /dev/block/mmcblk0p19: I/O error
Error opening: '/cache/recovery/ .version' (Read-only file system)
I haven't been able to Restore my backup because of the error above,
I haven't able to copy files to the internal storage
I haven't been able do anythings significant at the recovery
I can't install new ROM
here are some steps I have taken so far to help fix the problem but to no avail
I have flashed older versions of the custom recovery through fastboot but whenever I boot to the Recovery I still see the twrp 3.1.1 i flashed before the problem happened. Even though my command.exe tells me that the flash was successful but it doesn't overwrite the twrp 3.1.1
I have fastboot erased cache but nothing happened
I have tried to return the device to stock by RUU method but whenever I fastboot oem rebootRUU, the device powers off, reboots to white HTC logo attempts to boot phone instead of going into RUU mode.
I have a hunch that somewhat my internal storage is corrupted and is probably causing these problems but I don't know how to go round it.
Any help will be gratefully appreciated.
I don't think it's bootlooping, it just sits on the splash screen. I can still go to the bootloader and TWRP recovery. What's the best course of action?
I'm also seeing this behavior I think. I did:
1) ./flash-all with Android 9 factory image.
2) Reboot, turn on ADB access etc.
3) Install MagiskManager, latest version 6.0.0
4) Reboot into recovery, and install Magisk v17.2, everything seems okay.
5) Reboot system
After the reboot, it gets stuck on the Google logo and then eventually reboots into recovery...
Anyone else seeing something like this?
SOLUTION: Turns out I was still able to boot into eRecovery. From there I could reboot normally into the system. I then went into fastboot and flashed Blackball's TWRP 3.2.1-0 build for Oreo. Everything boots smoothly now.
Hello,
today I decided to try and flash the ResurrectionRemix-GSI to my Huawei P10 (EMUI 8.0) which was successful at first. I unlocked the bootloader, flashed TWRP via fastboot (First Link to TWRP in this thread). From TWRP I did a complete backup and wipe and installed ResurrectionRemix (ARM64 A-only from this thread). The system booted up just fine and everything seemed to work like a charm. I then went on to boot into recovery again, because I wanted to install the pico package from OpenGApps.
The problem now is that I'm stuck on the splash screen of TWRP. When I try to turn off the phone by holing the power button, it just reboots to recovery, which greets me with the everlasting splash screen. I have also tried rebooting the phone via adb -> same result. And to make it even better: When I try to get into fastboot mode via "adb reboot bootloader", I get thrown back into recovery as well.
My current "strategy" is to just drain the battery and hope for the best (well... I can't even turn the phone off anyway). I've read that other people have waited up to 6 min for TWRP's splash screen to dissapear. I'm waiting for roughly an hour now, so I'm pretty positive, that it's stuck.
Hope someone can help.
UPDATE: The battery has drained now. When I connected the phone to its charger, it went straight into recovery and is stuck again. Fastboot still doesn't work.
Huawei phones do not seem to go along very well with TWRP for installing GSIs. The original recovery is required to do a factory reset, before you can boot into system. Can you reboot in fastboot mode? If yes I would flash the original recovery and system from fastboot. It is clearly explained on the Openkirin.net website. I can also recommend flashing one of their GSIs, since they include the Huawei camera and nano Gapps.
M1chiel said:
Huawei phones do not seem to go along very well with TWRP for installing GSIs. The original recovery is required to do a factory reset, before you can boot into system. Can you reboot in fastboot mode? If yes I would flash the original recovery and system from fastboot. It is clearly explained on the Openkirin.net website. I can also recommend flashing one of their GSIs, since they include the Huawei camera and nano Gapps.
Click to expand...
Click to collapse
No, I can't boot into fastboot mode, at least not via adb (only method I know of). When I run "adb reboot bootloader" it just throws me back into recovery mode with the splash-screen stuck.
So I tried updating my M7 to TWRP 3.2.1-0 by flashing the img file using a slightly older version of TWRP
After installing, wiping cache & rebooting, my phone only gets to the HTC logo, with "Entering Recovery..." message at the top. It doesn't get any further than that. Even more annoying, my ADB has stopped detecting my phone so I can't flash anything else right now
Any help or advice?
Okay after leaving it alone for a while it's suddenly started to work perfectly and boot as normal again...!
Uhhh, I guess mods are free to delete/lock this thread?