Help, TWRP wont recover get past boot screen - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

So Ive been running CM13 and TWRP, when supersu tries to install via twrp and boot loops the phone, went to reinstall the os but had an issue with twrp and now twrp wont boot up proper, and the os wont let me get past setup because of the stupid dropdown menu. before I factory reset is there a way to odin in and repair the recovery?
thanks
edit: eventhough the rooting process is so long, im just going to flash stock and start over. thanks.

Related

Stock on Samsung Logo with Custom Lock Image

I had Mint Jelly2.1 installed and everything was working fine.
it started when I had used the APK Hide It Pro. I was in the process of hiding videos and I noticed that my phone got rebooted and got stock in the Samsung boot up image with the Custom Lock image.
I tried nandroid restore, 2 images, but both also failed to restore / bootup.
I tried re-installing ROM and it was successful but during reboot, it will still get stock on the boot image.
Last step.
I used ODIN to restore the stock ROM and ODIN was able to install and reset. And my phone rebooted but still got stock on the Samsung Logo with CUstom Lock Screen.
What else can I do to fix this?
Thank you.
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
scott14719 said:
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
Click to expand...
Click to collapse
I had tried to restore/flash from recovery before ODIN and it all Failed.
Anyway, the last step ODIN restore and it was still stock at the Samsung Logo with Lock image.
I left the phone to charge the whole night and this morning when I turned it on, it was able to start properly with ODIN stock ROM.
I tried to go to recovery, and can only be done manually, and it was not the TWRP recovery but the stock one, with very small characters.
I tried to install Mint Jell2.1 right away but just reboots.
I realized that I might need to root it again and downloaded the Tool and re-loki'ed/rooted and installed TWRP.
Now, I am able to install Mint Jelly 2.1 and restoring all my apps.
I appreciate the comment.
Thank you.
scott14719 said:
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
Click to expand...
Click to collapse
Yeah, every single time I ODIN back to stock, I get stuck at the splash screen also. And rebooting to 3E (factory) recovery and "restore factory defaults" works great.
CZ Eddie said:
Yeah, every single time I ODIN back to stock, I get stuck at the splash screen also. And rebooting to 3E (factory) recovery and "restore factory defaults" works great.
Click to expand...
Click to collapse
I can confirm this works happened to me yesterday.
leoj85 said:
I can confirm this works happened to me yesterday.
Click to expand...
Click to collapse
I am running out of options. I thought I am already out of this stuck on Samsung Logo with Custom Lock icon.
I had ODIN to stock I337UCUAMDL and reset, Ran Loki patch / installed TWRP, intermittently it will get stuck.
I flashed Shoshock 1.9, was able to reboot and setup basic settings.
I manually reboot to check if it was able to fix the problem, but no.
I am stuck again and don't know what is the next step for trouble shooting it.
any advise will be appreciated.
Thank you.
I got stuck to 1st boot image of Samsung with Lock Custom Icon.
I did format data/factory reset/clear cache/dalvik.. all of the wipe ootions.
I flashed a new ROM, successful, rebooted pass the logo and booted fine. I did not change any settings yet and I rebooted to check if it will get stuck again and sure after reboot, it got stuck again on the 1st image that shows up : Samsung Logo with the Lock Custom Icon.
qwer43 said:
I am running out of options. I thought I am already out of this stuck on Samsung Logo with Custom Lock icon.
I had ODIN to stock I337UCUAMDL and reset, Ran Loki patch / installed TWRP, intermittently it will get stuck.
I flashed Shoshock 1.9, was able to reboot and setup basic settings.
I manually reboot to check if it was able to fix the problem, but no.
I am stuck again and don't know what is the next step for trouble shooting it.
any advise will be appreciated.
Thank you.
Click to expand...
Click to collapse
IMPORTANTwhen using*twrp*recoverydo not choose "format data"(that option will ask you to type "yes")what if i did?rom will not boot past "padlock" boot screen orrom will not boot on second reboot*help!! I did, I did*1. sigh2. d/l odin3. d/l odin stock restore MDL4. let it do its thang5. after its complete it will be stuck at padlock6. should have "rtfm" huh?*7. pull battery8. hold home button, vol-up, power at same time9. when phone vibrates, release power, while still holdingvol-up, and home button10. you will now be in "stock recovery"11. wipe factory reset then wipe cache12. reboot*13. swear you will never "ignore instructions"

[Q] [Help] LG G2 stuck on Recovery Mode.

Hello everyone and I apologize if there's been a solution to this before but I couldn't find it.
I was on Rooted stock V20F, and there was a new OTA update from LG (around 110 MBs). Before installing anything i made a backup from TWRP Recovery just in case anything went bad.
So after I download the official update, the phone reboots, and boots into TWRP recovery. From that moment, I can't get the phone to boot properly no matter what I do.
I tried restoring my backup, the phone will still boot into TWRP. Tried Factory Reset, Format Data, installing a new custom rom and nothing. It always brings me back to TWRP.
Also when i try to get into download mode so I can flash a KDZ file with flash tool, it boots into TWRP again.
Any ideas? Thanks a lot in advance.
edit: I actually found the solution here (it wasn't in the troubleshoot section and I didn't notice it..): http://forum.xda-developers.com/showthread.php?t=2451696
Is there any way to install official OTA updates without the phone freaking out?

[Q] ODIN fails while installing TWRP, stuck at boot

I was trying to upgrade from CM11 to CM12, which went smooth except for GAPPS closing constantly. I read online that this was caused by an old version of the recovery, so I tried to update TWRP to 2.8.4.0. I first tried using the TWRP app from the Play Store (after recovering my Nandroid backup), which locked the phone where it would only try booting into recovery, but couldn't get there. Holding the power button to turn it off would result in a reboot right back into recovery, which of course never went anywhere. Now I am trying to re-install TWRP using ODIN but It fails every time [Complete(Write) operation failed.] I have an early S4 from AT&T and it has never had an official update. I can't remember which firmware it is using, but it is the original so I shouldn't have any problems there. Can anybody help me get this thing up and running with either TWRP or CWM and CM12 please?!
Update: I have been able to get the phone to boot by first booting into Download mode, then hitting the Volume Down button to cancel. This has twice booted it back into the OS. Still no recovery though.
Solved
I was able to install TWRP 2.8.4.0 from the app after getting the device to boot. It worked correctly this time and all appears to be well. Odd that ODIN didn't work though.

Lack of recovery

Hey guys, I'm a longtime XDA browser but hardly ever post. I have the MXPE rooted with the newest TWRP build and has been running great since I got it. last night flashed the Deodexed 6.0 build from AICPs 5.1.1. I had some issues with the SD card being mounted as internal storage and erasing something so I tried to flash back to stock as my nandroids weren't seen as usable.
Long story short when I flashed back to stock, the recovery would never take. I've flashed the stock recovery and twrp to no avail. For some reason it wont actually stick. Everything else is back to stock but that. When I used the win toolkit and tried to flash twrp again it said something about the folder locations so I'm wondering if I messed something in the partitions.
Question is, have you guys ran into this issue or have any insight on where to go from here? I've looked around but I couldn't find a post that the same as this issue. As a side note, I can get into the bootloader just fine.
I appreciate any info that someone can provide.
Flash twrp. Reboot back to recovery from recovery. Reboot system.
Hopefully it's that easy. Stock os flashes stock recovery on boot. Rebooting recovery from recovery prevents that from happening.
From TWRP:
"Note many devices will replace your custom recovery automatically during first boot.... Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
mxpe 6.0
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
THEFILLTER said:
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
Click to expand...
Click to collapse
I'm sorry I didn't see this sooner. Flash recovery with fastboot. Boot into recovery. From reboot menu in recovery, select reboot recovery. Twrp will patch so recovery isn't lost again.
mxpe 6.0
That did it. thanks alot ffejy462!

Phone stuck in bootloop!

So i started to update viper4android and i accidentally pressed volume up which tries it to install via AROMA now my phone is stuck on bootloop, it just keeps rebooting to recovery trying to install the viper4android, is there any possible way to get out of this or my phone is dead?
Any help will be appreciated,
TIA
a safe haven said:
So i started to update viper4android and i accidentally pressed volume up which tries it to install via AROMA now my phone is stuck on bootloop, it just keeps rebooting to recovery trying to install the viper4android, is there any possible way to get out of this or my phone is dead?
Any help will be appreciated,
TIA
Click to expand...
Click to collapse
You didn't specify your exact phone model, so assuming KLTE
AFAIK aroma does not work well with our TWRP
Can you pull the battery and then boot directly to recovery so you can wipe system/cache/Dalvik and then flash the ROM again?
If recovery is messed up, can you pull battery, then boot to download mode so you can reflash TWRP in Odin/Heimdall, or better yet flash latest stock Rom (caution if you have a g900V/A with stock locked bootloader) in Odin/Heimdall, followed by TWRP?
Post again if you need more help, and try to include as many specifics as possible eg exact phone model, TWRP version, Rom zip filename, Gapps, etc. I'll try to help if I can
I am very sorry for not posting the model number, mine is G900I (KLTEDV), everytime i turn on the phone it just keeps booting onto the recovery and goes to install the viper4android but it fails to do that and reboots again and again, its impossible to do anything basically, not booting onto the rom or anything. Recovery version is TWRP 3.2.2-0, it opens up directly to the zip file which is viper4androidfx-aroma.zip and tries to flash it and crashes and the whole process starts again, pulling the battery didnt break the chain it just keeps rebooting to do that again!
I reflashed a new twrp recovery ver 3.2.3-0, but it still tries to flash that zip file again! Even after deleting the file itself it still tries to flash it and keeps rebooting!
How do i get rid of this twrp loop!? This is so weird!
P.S: After reflashing twrp the phone boots to the rom normally but i cant access recovery anymore, whenever i go to recovery it goes on in an infinite bootloop (cleared cache and dalvik cache using es explorer root), I am also on LineageOs 16.0, tried stock recovery but the stock recovery also keeps bootlooping.
P.S this viper4android is a magisk module!
NVM, solved it by flashing stock rom! Thanks!

Categories

Resources