Database Users

Won't boot to TWRP recovery after flashing to 4.3

Hi all, I'm new here (great place, very informative) and pretty new to the Android scene in general.
As the title said, My AT&T S4 won't boot to recovery after I flashed 4.3 JWR663. Worked fine before and 4.3 is working great, but I can't get to TWRP. When I hold "power + volume up" I get the blue text dialog indicating its going to boot to recovery and the phone just shuts off. I can boot to download mode, but haven't done anything out of fear. I'm not rooted (which is what I'd like to do once this is fixed).
Should I try and re-flash TWRP? Any other suggestions? Feel free to break it down like you're talking to a child. Thanks in advance.

Try flashing it. Get goomanager from the play store. Open it and hit the menu button. Hit install openrecoveryscript.
Sent from my SGH-I337 using xda premium

graydiggy said:
Try flashing it. Get goomanager from the play store. Open it and hit the menu button. Hit install openrecoveryscript.
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
Will that work without root?

Vikingod said:
Will that work without root?
Click to expand...
Click to collapse
You'll need root to flash a recovery with GooManager.
How did you install 4.3? I assume that it's a custom 4.3 as I don't think it has been officially released yet. If it's custom, I'd assume that the ROM had been rooted as well...

theSpam said:
You'll need root to flash a recovery with GooManager.
How did you install 4.3? I assume that it's a custom 4.3 as I don't think it has been officially released yet. If it's custom, I'd assume that the ROM had been rooted as well...
Click to expand...
Click to collapse
I was rooted, but the ROM had it removed and I need to flash Chainfire to get it back. But I can't get into recovery to do so. I think the ROM was done by Jah0n
Is it safe to flash TWRP with Odin now? If so, could you point me to the directions to help me do so. Thanks again for the help.

Found a fix!
My recovery is fine. All I did was power down, try to boot into recovery with "power + volume up + home" and just when the phone vibrated to boot into recovery, I let go of the power button but continued holding the other buttons. It booted into TWRP just fine.

Vikingod said:
Found a fix!
My recovery is fine. All I did was power down, try to boot into recovery with "power + volume up + home" and just when the phone vibrated to boot into recovery, I let go of the power button but continued holding the other buttons. It booted into TWRP just fine.
Click to expand...
Click to collapse
Yep, that's the way you're supposed to get into recovery.

I an able to get in with only power+vol up. Both work for me.
Sent from my SGH-I337 using xda premium

Vikingod said:
Hi all, I'm new here (great place, very informative) and pretty new to the Android scene in general.
As the title said, My AT&T S4 won't boot to recovery after I flashed 4.3 JWR663. Worked fine before and 4.3 is working great, but I can't get to TWRP. When I hold "power + volume up" I get the blue text dialog indicating its going to boot to recovery and the phone just shuts off. I can boot to download mode, but haven't done anything out of fear. I'm not rooted (which is what I'd like to do once this is fixed).
Should I try and re-flash TWRP? Any other suggestions? Feel free to break it down like you're talking to a child. Thanks in advance.
Click to expand...
Click to collapse
Did you try manually booting into recovery with the power and volume button?

quattros said:
Did you try manually booting into recovery with the power and volume button?
Click to expand...
Click to collapse
He fixed his problem a few posts ago...
Sent from my SGH-I337 using xda premium

I have an older phone and after flashing the twrp recovery it won't let me boot into recovery mode at all can someone please give some advice on how I should fix this?

Which phone do you have?

An Alcatel One touch POP D3 4037A

Try using the Alcatel mobile tool to flash back to stock.

TWRP doesn't work

My LG G3 running lineage os 14.1 won't boot into TWRP.
graydiggy said:
He fixed his problem a few posts ago...
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
The blue and black screen start up screen comes up. But it stays like this. This happened since I flashed the lineage ROM. What should I do?

my phone agua rio 4.4.2 kitkat .
After flashing twrp recovery img .
After rebooting it .twrp not installed and it only reboot normal i didnt get to twrp recovery
Need solution pls pls

This thread is about the Samsung Galaxy s4.

Hi there. I'm new of this forum and even of the Android customization scenario. I have a Samsung Galaxy s4 i-9505 with 5.0.1 firmware and build LRX22C.I9505XXUHPK2. I've tried to install TWRP with Odin3 (so without root my phone) and all the procedure goes well. After reboot, I have turned-off my phone and I've tried to enter in the TWRP's recovery mode (using the combo buttons: VolumeUP + Home button + Power button) but the "TEAMWIN" logo didn't appear and the normal "Android Recovery Menu" were visualized.
I need some help to undestand if I did some mistakes during the flashing process. I've used the last versione of TWRP (3.1.1-0 for jfltexx). Any help will be appreciated. Thanks for your attention to this matter.

If you want to root with TWRP, try this for the gt-i9505:
open Odin 3.07 and uncheck everything except r reset time;
download the tar version of twrp for the gt-i9505: https://dl.twrp.me/jfltexx/
download the latest version of supersu.zip and copy it to an sd card or the phone's internal storage: http://www.supersu.com/download;
place the sd card in the phone if twrp has been saved to the sd card from the step above;
connect the phone in download mode and flash twrp in Odin's PDA slot;
when you see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery, install supersu.zip, reboot.
If you just want to install a custom ROM, copy the ROM to the internal or external sd card, install twrp, and install the ROM. Root is not required to install a custom ROM, only a custom recovery.
Warning: whenever you flash anything to a phone, it is always possible for something to go wrong and you must be prepared to deal with any consequences. I have used this method for several note 2, note 3, s3, and s4 phones without any issues. With this being said, I can't guarantee that the above steps will work for your phone or your phone won't be bricked.

Recovery won't flash

I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4

Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.

SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4

T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps

Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4

T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.

Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4

T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.

OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.

[Q] Trouble installing custom recovery on D800

I rooted using ioroot12 and tried installing recovery using both play store CWM installer for D800 as well as a manual install using the method shown in a thread in the D800 development forum. Both methods appear to install successfully but when I reboot to recovery I get a black screen (can tell black light is lit though) and nothing else. Holding the power eventually reboots phone back into the stock os. When in the broken recovery status and connected to computer via USB I get a slew of drive letters all prompting to format.
I'm guessing those are all the directories on the phone which are formatted android fs?
Any ideas what is happening? ioroot12 contains some changes to be compatible with the latest OTA, maybe the stock recovery file structure changed a little after the OTA?

arie001 said:
I rooted using ioroot12 and tried installing recovery using both play store CWM installer for D800 as well as a manual install using the method shown in a thread in the D800 development forum. Both methods appear to install successfully but when I reboot to recovery I get a black screen (can tell black light is lit though) and nothing else. Holding the power eventually reboots phone back into the stock os. When in the broken recovery status and connected to computer via USB I get a slew of drive letters all prompting to format.
I'm guessing those are all the directories on the phone which are formatted android fs?
Any ideas what is happening? ioroot12 contains some changes to be compatible with the latest OTA, maybe the stock recovery file structure changed a little after the OTA?
Click to expand...
Click to collapse
i repeatedly tried over and over after the ota.... it wont work you have to go back to stock reset. root then install twrp or cwm. twrp worked for me and cwm messed up my device causing a complete wipe of everything including logos and everything just a black screen that wouldnt power on. 30 minutes later it booted back up??? be careful.

Thanks
podagee said:
i repeatedly tried over and over after the ota.... it wont work you have to go back to stock reset. root then install twrp or cwm. twrp worked for me and cwm messed up my device causing a complete wipe of everything including logos and everything just a black screen that wouldnt power on. 30 minutes later it booted back up??? be careful.
Click to expand...
Click to collapse
Thanks, probably saved my phone from certain destruction. I followed the steps to go back to stock and successfully rooted and was able to install custom recovery finally.
I seem to recall the OTA taking a long time for being so small, I wonder if they played with partition sizing or something on the "o" firmware.

arie001 said:
Thanks, probably saved my phone from certain destruction. I followed the steps to go back to stock and successfully rooted and was able to install custom recovery finally.
I seem to recall the OTA taking a long time for being so small, I wonder if they played with partition sizing or something on the "o" firmware.
Click to expand...
Click to collapse
i only seen that the att apps were updated after the update as well as a security update tightening up their security for their bootloader.as far as partitioning uncertain on that.
glad it worked for you.

I spent a few hrs last night into the am trying to root and flash a working recovery. Just realized my phone auto updated to the OTA and, think I need to go back to the pre-ota. For whatever reason, I can't get twrp to update, no matter how I try to flash it.
Sent from my LG-D800 using Xparent Red Tapatalk 2

bzmotoninja83 said:
I spent a few hrs last night into the am trying to root and flash a working recovery. Just realized my phone auto updated to the OTA and, think I need to go back to the pre-ota. For whatever reason, I can't get twrp to update, no matter how I try to flash it.
Sent from my LG-D800 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
I got mine to root using ioroot 12. I got twrp by usint freegee app. The only thing is my recovery is 2.6.3.0. Trying to figure 9ut how to get a newer version of recovery now.
Sent from my LG-D800 using XDA Premium 4 mobile app

Check with the guys on the webchat If you get stuck. I gotta flash pre-OTA personally. Something that I flashed stuck and won't let twrp update.
Sent from my LG-D800 using Xparent Red Tapatalk 2

bzmotoninja83 said:
Check with the guys on the webchat If you get stuck. I gotta flash pre-OTA personally. Something that I flashed stuck and won't let twrp update.
Sent from my LG-D800 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
If you're on 10o now, try using FreeGee from the Play Store, as mentioned, to get twrp installed.

heres what youre failing to realize..... with 2.6.3.0 I cant flash anything other than, nothing. Everything fails..... I cannot upgrade to the later versions of twrp, any way shape form or fashion. thanks tho

btm fdr said:
If you're on 10o now, try using FreeGee from the Play Store, as mentioned, to get twrp installed.
Click to expand...
Click to collapse
I couldn't get the 10o OTA to install but I used FreeGee to install TWRP and it was incredibly easy/simple. I've seen a few people now that have said they were also able to flash TWRP after upgrading to 10o using FreeGee as well.
fountain79 said:
I got mine to root using ioroot 12. I got twrp by usint freegee app. The only thing is my recovery is 2.6.3.0. Trying to figure 9ut how to get a newer version of recovery now.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you have TWRP installed already you can just boot into recovery, flash a new TWRP or CWM recovery zip and then go to the "Advanced" menu and select Reboot>Recovery to boot into recovery again and you'll be in the new recovery you just flashed.

I tried that like 30 times over the last 2 days. I finally got flashtool to go back pre ota and now I'm running PA and have 2.6.3.3 for twrp. My reason for things not working is, I think that when I flashed something, it stuck making the code all jacked. Please next time, don't ASSume that because its supposed to work that it always will. There will always be human error.
Sent from my LG G2 using Xparent Red Tapatalk 2

Recovery issue

I have successfully rooted my sm-n900t but whenever I try to boot into recovery an endless loop occurs. Can anyone help me?
Sent from my SM-N900T using Tapatalk

re: bootloop
HowlTowardsTheMoon said:
I have successfully rooted my sm-n900t but whenever I try to boot into recovery an endless loop occurs. Can anyone help me?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Assuming that your phone is rooted and working properly except for the bootloop
issue you are having when trying to get into recovery, do the following...
Go to the playstore and download "goomanager" a free app
and click the menu softkey on left side of phone then select
"flash open recovery script".
Then wait til it gets done and when it's done just reboot the phone.
That's the easiest way to solve your bootloop issue.
Another good free app you can use is "TWRP Coordinator" which
you can download from the playstore too, after installing this app
simply select the option to flash twrp recovery then after it gets
done simply reboot the phone.
Good luck!

Misterjunky said:
Assuming that your phone is rooted and working properly except for the bootloop
issue you are having when trying to get into recovery, do the following...
Go to the playstore and download "goomanager" a free app
and click the menu softkey on left side of phone then select
"flash open recovery script".
Then wait til it gets done and when it's done just reboot the phone.
That's the easiest way to solve your bootloop issue.
Another good free app you can use is "TWRP Coordinator" which
you can download from the playstore too, after installing this app
simply select the option to flash twrp recovery then after it gets
done simply reboot the phone.
Good luck!
Click to expand...
Click to collapse
I will try this out now and get back to you thanks for the quick response!
Sent from my SM-N900T using Tapatalk

I have checked that I am rooted with root checker.
I installed twrp via Odin and tried to reboot into recovery and I am still stuck in an endless loop.
I get a message saying
"Recovery is not seandroid enforcing"
Any help?
Sent from my SM-N900T using Tapatalk

Bump could someone please help?
Sent from my SM-N900T using Tapatalk

Custom kernel and root

I flashed a custom kernel and rooted my phone, still using stock rom. Will I get Lollipop on OTA update?
Thanks.

jjforums said:
I flashed a custom kernel and rooted my phone, still using stock rom. Will I get Lollipop on OTA update?
Thanks.
Click to expand...
Click to collapse
Nope you have to go back to stock and lock your bootloader
Sent from my Nexus 4 using XDA Free mobile app

phetam said:
Nope you have to go back to stock and lock your bootloader
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
That is incorrect, you can get an OTA with an unlocked bootloader, but you must have stock recovery on an official ROM. If you are already rooted it is a coin toss, depends what has been changed, it may work or it may fail, but you will lose root.
That being said, many root methods replace recovery, so it is best to not take an OTA if you have modified your system from stock if you really don't know what you are doing, either flash stock images when they come available manually, or wait and flash radios/bootloader manually and use a custom ROM... it is, after all, a Nexus device.

acejavelin said:
That is incorrect, you can get an OTA with an unlocked bootloader
Click to expand...
Click to collapse
TIL, thank you.
Sent from my Nexus 4 using XDA Free mobile app

So... How to get stock recovery/kernel/rom back? I'm running stock rom with cwm and semaphore kernel.

jjforums said:
So... How to get stock recovery/kernel/rom back? I'm running stock rom with cwm and semaphore kernel.
Click to expand...
Click to collapse
Easiest to download the lollipop factory image and flash in bootloader, then you don't need OTA. Backup your data first!
If you insist on using the OTA, you'll have to first lay your hands on flashable zips / images of Stock recovery and kernel, flash them in cwm/ bootloader, then install the OTA.
Theres also a flashable zip of lollipop (search for thread in xda) that you can flash in cwm.

Tried to use fastboot (flashed bootloader) but I got no menu in recovery options, when I chose 'Recovery mode' in bootloader, I only see that dead android with a question mark, but nothing happens when I press volume down or volume up. Any idea?

jjforums said:
Tried to use fastboot (flashed bootloader) but I got no menu in recovery options, when I chose 'Recovery mode' in bootloader, I only see that dead android with a question mark, but nothing happens when I press volume down or volume up. Any idea?
Click to expand...
Click to collapse
The dead android screen is the stock recovery, to see the menu press and hold Power button, then press volume up.