My I747 has been running ok with twrp 2.8.7. and cm 12(latest). After I used twrp manager to install twrp 3.0.1, twrp will boot loop whenever recovery is booted. if I reboot at this point (no buttons except pwr) the system goes to recovery again. I am then able to boot back to download mode via buttons and then continue to rom. I have also tried 3.0,2 and 2.8.7, all the same. I have installed the same set of twrps with flashify, same problem. I then restored a philz bckup from flashify which boots ok. I then installed cwm recovery (newest version) from flashify which boots ok. Basic issue is no recent twrp version will install without going into loop. Any help/thoughts appreciated!!!
i believe an older bootloader can cause this issue. which bootloader/modem are you on ?
"err on the side of kindness"
Related
What I was trying to do: I have a stock 4.4.2 AT&T GS3 that I wanted to root, and then install Cyanogen Mod.
What I did: I flashed Auto-Root with Odin 3.10, restarted and then flashed TWRP 2.8. I then booted to TWRP and attempted to wipe/format the phone but it showed some errors along the way, I think it was something having to do being unable to mount the SD card. I then rebooted into recovery and flashed CM12 and slim Google Apps zip. When it was flashing both I got a string of errors but it said it was successful.
Where I'm at now: When I try turning the phone on (without holding any buttons down) it attempts to boot straight to the TWRP but gets stuck at the blue TeamWin screen. I'm able to get to download mode by holding down the appropriate buttons. I'm wondering if there's anything I can flash from Odin to resolve this.
I also realized I have unbacked up photos on the device, I don't think the format was successful, is there any way to recover those?
Thanks
To recover the pictures, try re-installing TWRP, boot into TWRP, and mount the partitions. Connect the phone to your computer and copy your pictures.
TWRP
I have had this happen before. Try using Odin to flash an older version of TWRP, uncheck reboot after flash and then when it is done, do a battery pull. This has gotten me back into a working TWRP to restore my previous setup. Note: You made need to go back to 2.6. Once you have gotten back up and running flash to the current TWRP with the app.
I've recently flashed the latest twrp on my oneplus3 a3003 through fastboot. All fine, I flashed the cyanogenmod 14.1 and the gapps 7.1 over the oxygen os. Now I tried to boot into recovery to flash the pixelfy zip file, but I found out that I can't access recovery mode. All I get is boot logo and the capacitive buttons illuminated for a while, then the screen goes off and I have to press the power button for 6/7 seconds. I tried reflashing the recovery.img through the terminal and no result, I tried through TWRP manager, it says successful but the result is still the same. Ah, before installing the twrp I hard bricked the device and I unbricked it, so to me it's like a corrupted partition. Is there a way to restore twrp (or to restore the recovery partition, still being able to flash twrp) without losing data? If no, is there a way to restore it to a funcional state without having to use qualcomm drivers? If no, is there a way to restore it to a funcional state AND keep it that way?
I solved it. Basically the cm14.1 version was blocking twrp or any other recovery aside from the cm recovery. I found a fixed version of the twrp somewhere.
Vas0sky said:
I solved it. Basically the cm14.1 version was blocking twrp or any other recovery aside from the cm recovery. I found a fixed version of the twrp somewhere.
Click to expand...
Click to collapse
Is it possible that you gave me this recovery? I'm looking for one too same problem as you
Thanks
http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Here you go.
I have a Samsung Galaxy Note 3 with Android 5.0 (Lollipop) and Rooted.
I've been trying to flash CWM and also TWRP without success.
I've used all sorts of methods, Odin, ROM Manager, Nandroid Mgr, Flashify, ADB, ... with the same results:
The flashing always seems to be successful but when rebooting into the custom recovery mode, the custom interface doesn't appear but instead, the system tries to boot into what it appears to be the stock recovery's three first colored text lines for a few seconds and it reboots into a loop until I remove the battery.
Then the only way to get back to the system is boot in download mode, flash either CWM or TWRP with Odin (although I know they won't actually work) and it then reboots into system.
Then I restore a backup of the stock recovery that I luckily made with Flashify and at least the stock recovery works.
(BTW, when the stock recovery has been restored, if I go to ROM Manager both CWM and TWRP are listed as "Already Installed" ... I thought that when you flash the stock recovery, any previous custom recovery is removed )
Any help would be appreciated
After I flashed TWRP and went to the recovery right after flash, TWRP booted and I did decrypt + allow mods. Once I booted to system and later booted to recovery, TWRP didn't boot and stock recovery booted. Any help?
What I'd try is boot twrp, fastboot boot twrp.img. Then install supersu in twrp. Then boot back into the bootloader and flash twrp.
BearOfXDA said:
After I flashed TWRP and went to the recovery right after flash, TWRP booted and I did decrypt + allow mods. Once I booted to system and later booted to recovery, TWRP didn't boot and stock recovery booted. Any help?
Click to expand...
Click to collapse
I'm guessing you are still on the stock ROM and kernel? Flash a different kernel, or depending on flashing root it might modify the boot.img and stop it from doing that too.
So, I successfully unlocked the bootloader, then followed the instructions to install TWRP (which worked initially because I was able to access TWRP immediately after flashing). But how to I access it again once I'm back in the OS? When I click reboot to recovery it always reverts back to the stock recovery. I'm still on the stock OS, but I just assumed once TWRP was installed I could boot into it from there. What am I missing?
Solved the problem by getting Magisk installed and using Flashify app to flash the downloaded TWRP img.
@brGabriel just use the fastboot commands as mentioned by manojpawarsj12;
fastboot flash recovery twrp.img
Don't mess around with Flashify, it's dated and a good way to brick your phone...