Unable to access recovery on Samsung LTE-A build 14.1-20170719. - LineageOS Questions & Answers

I was able to update my phone to that build, but when I tried to access TWRP to install the latest build, I'm stuck on the twrp screen, I even Installed the official TWRP app, and reinstall the LTE-A version from there, but I'm still having the same issue. Please help.
Sent from my SM-G906S using Tapatalk

Related

[Q] Recovered my Nexus 7 to 4.4.4 but can't find any recovery mode

Guys I am facing this weird issue. Earlier I had TWRP installed on my nexus 7 with android 4.4.2 but since I was unable to install any OTA updates for 4.4.4 I figured maybe it was an issue with the TWRP so I wanted to get rid of it. I used One Click Factory Restore 4.4.4 KTU84P tool in the dev forums and it kinda did restore my tab to a stock version. The issue is now when I try to boot into recovery mode, it shows an error logo and seemingly there is no recovery installed. How do I go to stock recovery from here? Any help will be appreciated.
Thanks
ammy_91 said:
Guys I am facing this weird issue. Earlier I had TWRP installed on my nexus 7 with android 4.4.2 but since I was unable to install any OTA updates for 4.4.4 I figured maybe it was an issue with the TWRP so I wanted to get rid of it. I used One Click Factory Restore 4.4.4 KTU84P tool in the dev forums and it kinda did restore my tab to a stock version. The issue is now when I try to boot into recovery mode, it shows an error logo and seemingly there is no recovery installed. How do I go to stock recovery from here? Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
If you mean by error logo, you see an image of an android on its back, that is recovery, stock recovery. You can still use the OTA with TWRP, so you pretty much wasted your time removing it, the only difference is with TWRP you have to flash the OTA manually (the OTA zip is located in /cache).
So reinstall the latest TWRP, and reroot, and have fun with 4.4.4.
If you want your device to be even more useful and future upgrades to be easier, instead of leaving normal TWRP on it, after rooting, install MultiROM along with its modified TWRP, and make your device even better.

Bootloop caused by SU binary update fail via TWRP. Please help!

I have an LG G3 running the latest CM 13 nightly with TWRP for a recovery.
Last night I went into the SU app on my phone and it said it needed an update (I was not connected the internet). I clicked update via TWRP and it went into TWRP. It ran some code and now it is stuck in a bootloop. It will boot to the CM logo with the pulsing light and will get no further. I've tried wiping cache and dalvic cache and that didn't work. Tried fixing permissions and that didn't work. Also tried factory reset via TWRP and that did not work also. Please help.
Try reflashing your rom
Sent from my HTC One M9 using Tapatalk
Flash an earlier build of su. When prompted select normal "NOT TWRP"
Sent from my XT1526 using Tapatalk
Why is this in the xposed section?
I am facing the same problem.
Tried factory resetting.Didn't work,still stuck on bootloop.
Somebody please help me out!

Kindle Fire HD 8.9 (Jem) stuck at TWRP startup screen

I've been using the Fire HD 8.9 (Jem) with CM (a 2015 version of CM 12.1) with TWRP 2.7.0 without much of a problem. Yesterday, I flashed the latest CM12.1 nightly (20161216 version) using the same TWRP successfully. After the initial loading, I tried to factory reset the tablet. Once the pad restarted, it goes into the TWRP startup screen, and doesn't load the touch interface. The startup screen will flash every 5 seconds or so. I can't go back to normal boot either. Can anyone help? Thanks.
Have you fixed this yet?
If not, I'm not certain, but could be a mismatch between your older TWRP version and the most recent CM12.1 nightly. Can you actually use TWRP? Did you make a backup prior to installing the newest CM version (always imperative to do)? If so and TWRP works, simply wipe everything and reinstall your backup. Then first update TWRP (I'm using v 3.0.0) by multiple methods and try again. Does you computer still see your Kindle? If so, download a newer version of TWRP to your computer, transfer it to the Downloads folder of your "SD Card" on internal storage, and flash from there using TWRP. Try to keep plugged in so that battery stays in good shape.
If you can't use TWRP, you'll have use Fastboot to flash a newer TWRP version from your computer. Look for instructions on how to setup and then use Fastboot if you've never used this before. Some drivers that your computer may or may not have will be required. Good luck!
wicozani said:
Have you fixed this yet?
If not, I'm not certain, but could be a mismatch between your older TWRP version and the most recent CM12.1 nightly. Can you actually use TWRP? Did you make a backup prior to installing the newest CM version (always imperative to do)? If so and TWRP works, simply wipe everything and reinstall your backup. Then first update TWRP (I'm using v 3.0.0) by multiple methods and try again. Does you computer still see your Kindle? If so, download a newer version of TWRP to your computer, transfer it to the Downloads folder of your "SD Card" on internal storage, and flash from there using TWRP. Try to keep plugged in so that battery stays in good shape.
If you can't use TWRP, you'll have use Fastboot to flash a newer TWRP version from your computer. Look for instructions on how to setup and then use Fastboot if you've never used this before. Some drivers that your computer may or may not have will be required. Good luck!
Click to expand...
Click to collapse
Can't use TWRP, fastboot don't work, tryed almost everything on this forum.
nickelocene said:
I've been using the Fire HD 8.9 (Jem) with CM (a 2015 version of CM 12.1) with TWRP 2.7.0 without much of a problem. Yesterday, I flashed the latest CM12.1 nightly (20161216 version) using the same TWRP successfully. After the initial loading, I tried to factory reset the tablet. Once the pad restarted, it goes into the TWRP startup screen, and doesn't load the touch interface. The startup screen will flash every 5 seconds or so. I can't go back to normal boot either. Can anyone help? Thanks.
Click to expand...
Click to collapse
I had the exact same problem but I got into fastboot mode by using this adb command
Code:
adb reboot bootloader
have you tried this yet?

[HELP] Get stuck in bootanimation &then only boot to TWRP after upgrade Magisk & TWRP

[HELP] Get stuck in bootanimation &then only boot to TWRP after upgrade Magisk & TWRP
I have sucessfully rooted my phone but yesterday when i upgraded Magisk from 16.4 to 17.1 and then flashed lasted TWRP, my phone some how corrupted .
After that I tried to flash Factory Image and boot TWRP portable -> Flash ElementalX 2.05 -> Magisk 17.1 -> VerifiedBootSigner-v8 -> Reboot but my phone get stuck in bootanimation about 5 min and then reboot to recovery. Then it will always boot back to recovery when I reboot.
I have searched here but couldn't find any solution.
I tried to flash ElementalX and TWRP only and my phone booting normally. But anytime I flash Magisk it can't.
Please help me, I don't know what to do next, Thank you and sorry for my bad English. :crying:
I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.
Cozmikk said:
I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.
Click to expand...
Click to collapse
What version of TWRP did you use?

Magisk wont uninstall

Hello friends Im new year can you help me? My magisk wont update to 22.1 so I think I need to reinstall it and flash the latest realme ui from software update at the same time
I have been trying to uninstall magisk even if I click restore IMG it shows stock boot img doesnt exist or clicking complete uninstall will do nothing no error message or anything.
What I tried so far is
-Uninstall.zip from twrp
-Uninstall.zip from magisk module using the build v21 v22 v22.1 but it was still there.
As of now I do not have access for computer so can I also ask.
Will I be able to flash the latest android 10 from Color OS A.19 using twrp?
I know that you cannot install ota without stock recovery but I saw sometimes on some thread that they are flashing latest builds using twrp so Im a little confused now.
My phone is RMX1993 Pie Color OS A.19

Categories

Resources