Droid Turbo (quark) is the device in question...
So over the weekend I attempted to boot into TWRP recovery and TWRP ended up in a bootloop. Never had this happen before (version 3.1.1-0 is installed). Attempted to reinstall version using Flashify, however Flashify hung up and stalled when I'd click on "search for file to flash" or whatever it's called. So I (successfully) flashed TWRP version 3.2.1-0 using the TWRP app, rebooted to recovery, and TWRP still bootlooped (showed that version 3.2.1-0 was installed). Using TWRP app I (successfully) reflashed the 3.1.1-0 version .img file I had saved from the first time I flashed TWRP months ago, rebooted to recovery, and TWRP still bootlooped (showed that version was again 3.1.1-0).
I'm fairly certain that some rogue apps I installed caused the issue. It's the only thing I can think of as to why TWRP is messed up. I've uninstalled the rogue apps with Titanium Backup, TWRP still bootloops.
Any ideas on what I've botched, and how to unbotch it? Phone otherwise works as it should booting up normally, running normally, etc. I'm just at a loss for any future tinkering I want to do since I can't get into TWRP to make or restore backups.
Related
First and foremost I'm running an unlocked Boot Loader. My phone is running Android 4.1.2 (Baseband VRBMF1) and stock kernel.
Awhile ago I unlocked my phone (Using EZ Unlock 1.2) and installed Clockwork recovery (EZ Recovery).
I'm trying to install some newer ROMs and most of them require TWRP. I downloaded TWRP and flashed it through ODIN.
When I rebooted TWRP won't mount any partition and it shows internal memory as 0MB.
I booted back into Android (yes it still booted) and installed CWM using ROM Manager. Now the interesting thing is, in ROM Manager under "Recovery Already Installed" it lists both CWM and TWRP as options.
I rebooted into CWM and it navigates my SD Card no issue. I rebooted in to Android and downloaded TWRP and uninstalled ROM manager. I flashed an older version of TWRP (2.7) and rebooted into recovery. Same issue. Won't mount partitions and can't navigate files.
Reboot into OS and go into TWRP Manager. TWRP Manager actually shows CWM as the recovery installed.
So by all accounts (according to Rom Manager and TWRP Manager) I have 2 recoveries installed. ROM Manager shows both installed and TWRP Manager shows CWM installed while I'm able to boot into TWRP.
TWRP is for all intents and purposes useless. CWM works normally.
TWRP - 2.8.0.1
CWM - 6.0.4.5
justinnotjason said:
First and foremost I'm running an unlocked Boot Loader. My phone is running Android 4.1.2 (Baseband VRBMF1) and stock kernel.
Awhile ago I unlocked my phone (Using EZ Unlock 1.2) and installed Clockwork recovery (EZ Recovery).
I'm trying to install some newer ROMs and most of them require TWRP. I downloaded TWRP and flashed it through ODIN.
When I rebooted TWRP won't mount any partition and it shows internal memory as 0MB.
I booted back into Android (yes it still booted) and installed CWM using ROM Manager. Now the interesting thing is, in ROM Manager under "Recovery Already Installed" it lists both CWM and TWRP as options.
I rebooted into CWM and it navigates my SD Card no issue. I rebooted in to Android and downloaded TWRP and uninstalled ROM manager. I flashed an older version of TWRP (2.7) and rebooted into recovery. Same issue. Won't mount partitions and can't navigate files.
Reboot into OS and go into TWRP Manager. TWRP Manager actually shows CWM as the recovery installed.
So by all accounts (according to Rom Manager and TWRP Manager) I have 2 recoveries installed. ROM Manager shows both installed and TWRP Manager shows CWM installed while I'm able to boot into TWRP.
TWRP is for all intents and purposes useless. CWM works normally.
TWRP - 2.8.0.1
CWM - 6.0.4.5
Click to expand...
Click to collapse
Yes...exact same situation as me. I like 4.1.2....really hope dees can help us. I'd do it if I knew how. Lol
I said it in another thread but the issue appears to be related to the kernel for the recovery not being able to read the eMMC chip.
justinnotjason said:
First and foremost I'm running an unlocked Boot Loader. My phone is running Android 4.1.2 (Baseband VRBMF1) and stock kernel.
Awhile ago I unlocked my phone (Using EZ Unlock 1.2) and installed Clockwork recovery (EZ Recovery).
I'm trying to install some newer ROMs and most of them require TWRP. I downloaded TWRP and flashed it through ODIN.
When I rebooted TWRP won't mount any partition and it shows internal memory as 0MB.
I booted back into Android (yes it still booted) and installed CWM using ROM Manager. Now the interesting thing is, in ROM Manager under "Recovery Already Installed" it lists both CWM and TWRP as options.
I rebooted into CWM and it navigates my SD Card no issue. I rebooted in to Android and downloaded TWRP and uninstalled ROM manager. I flashed an older version of TWRP (2.7) and rebooted into recovery. Same issue. Won't mount partitions and can't navigate files.
Reboot into OS and go into TWRP Manager. TWRP Manager actually shows CWM as the recovery installed.
So by all accounts (according to Rom Manager and TWRP Manager) I have 2 recoveries installed. ROM Manager shows both installed and TWRP Manager shows CWM installed while I'm able to boot into TWRP.
TWRP is for all intents and purposes useless. CWM works normally.
TWRP - 2.8.0.1
CWM - 6.0.4.5
Click to expand...
Click to collapse
I recently installed TWRP Manager (from Google Play) on my StraightTalk Galaxy S3. Using that app, I installed TWRP v2.8.7.0 (twrp-2.8.7.0-d2vzw.img), which is for the Verizon Galaxy S3. It now mounts the partitions correctly. You might try that and see if it works for you.
I have a 703L 16Gb on B012 and installed X2-B015-KangVIP ROM through TWRP.
All installed fine and I tried the ROM for a while.
Anyway there were too many Chinese Apps so I restored my TWRP backup and rebooted.
Now it continually boots into TWRP and won't even power off. I tried again to restore it, and earlier backups, but they all just boot into TWRP continually.
Any suggestions? I tried using a stock Recovery but the phone wont even boot into that, so reverted back to TWRP.
Daver69 said:
I have a 703L 16Gb on B012 and installed X2-B015-KangVIP ROM through TWRP.
All installed fine and I tried the ROM for a while.
Anyway there were too many Chinese Apps so I restored my TWRP backup and rebooted.
Now it continually boots into TWRP and won't even power off. I tried again to restore it, and earlier backups, but they all just boot into TWRP continually.
Any suggestions? I tried using a stock Recovery but the phone wont even boot into that, so reverted back to TWRP.
Click to expand...
Click to collapse
You will back to Stock B112 with your TWRP Backup?
I think you must be flash the Boot img via fastboot,i think this fix the Problem.
Yes that worked thanks.
Hi all,
Recently I updated my Nexus 5 from Lollipop to Marshmallow 6.0.1 (MMB29Q) - latest build.
everything stock works fine but, once I flash a customer recovery, in my case TWRP it stops working...I get either a startup loop or TWRP gets erased by stock recovery.
I tried various steps ...
flashed TWRP 2.8.7.1 - rebooted to boot loader was able to get into TWRP but, once I reboot system, everything works but TWRP is gone/erased and replaced by stock recovery?
Flash TWRP 2.8.7.1, then flash latest TWRP 3.0, reboot to boot loader and can get into TWRP but once i reboot into system, I am stuck on the initial boot loop.
I have to start from scratch of flashing system and boot etc to get past the loop and it still replaces TWRP with stock recovery.
I can always get into Fastboot but when I go to recovery it seems its being replaced by stock recovery.
anyone experiencing this issue? thanks for your help.
I guess I am doing something stupid but, not sure what...and thanks for your help
If you give more detail on the steps you are taking it will be easier for someone to help. Also, have you tried doing a factory reset when it bootloops?
thanks for the response..here are the details..
I had Lollipop with TWRP 2.8.7.1
yesterday, I downloaded latest build from android site...extracted all files....booted into bootloader and flashed all files..
rebooted - Marshmallow works perfectly...offcourse it not rooted yet or its locedback due to this flash
Scenario:1
So downloaded TWRP 2.8.7.1 and flashed it as recovery, no errors nothing...i rebooted to bootloader and went to recovery to confirm TWRP is there
I rebooted the system - TWRP gives option to root which I said yes so its rooted. I reboot system, this goes into bootloop - I wait for say 5-10 min in this loop mode and I see that adb can recognize the device but nothing else....its stuck in loop
when I force shut down by holding power button for few sec - and go back bootloader/recovery - TWRP is still there
***note*** I did factory wipe in TWRP but that did not fix above condition.
Scenario2:
exact same steps but after I flashed twrp2.8.7.1, I rebooted bootloader and flashed twrp 3.0 as well confirmed twrp 3.0 is flashed and rebooted system - phone start normally no issues - when I restart to bootloader - no TWRP exists, its replaced by stock recovery
Scenario 2, I tried couple of other ways and still the same thing happens - twrp 3.0 get erased.
not sure what I am doing wrong but TWRP doesn't stick
since this is my active device - i flash system.img and boot.img to get the phone to working condition
thanks for your help
Try flashing the latest supersu to get root.
audit13 said:
Try flashing the latest supersu to get root.
Click to expand...
Click to collapse
That did the trick.....thank you very much. I was using older version of supersu thinking it was latest.....I downloaded V2.65 and installed it and that fixed all my troubles..
muchas gracias
Hello,
I encountered a annoying problem with my oneplus 6 tonight, a device i am fairly new with, previously owning a oneplus 3t.
While restoring a TWRP backup out of lazyness i screwed up something in my device to the point that it was booting in TWRP on the second try (the first was just a bootloop).
I said ok, there's something wrong, lets do that again and booted in TWRP (blu_spark, latest). There, i was not asked about any decryption password and obviously everything was encrypted.
I re-installed everything now using MSM tool and re-rooted but this is a painful process that takes time.
Anyone encountered that?
I am, and was on latest OOS with stock kernel, latest TWRP blu_spark (the stock one gives me QUALCOMM CrashDump when trying to boot from fastboot in it), rooted with magisk (latest 18.1) and using magisk custom rom on top of stock (XXX_nolimits, latest).
Any of you encoutered this issue?
Thanks!
0xPraeT0Rian said:
Hello,
I encountered a annoying problem with my oneplus 6 tonight, a device i am fairly new with, previously owning a oneplus 3t.
While restoring a TWRP backup out of lazyness i screwed up something in my device to the point that it was booting in TWRP on the second try (the first was just a bootloop).
I said ok, there's something wrong, lets do that again and booted in TWRP (blu_spark, latest). There, i was not asked about any decryption password and obviously everything was encrypted.
I re-installed everything now using MSM tool and re-rooted but this is a painful process that takes time.
Anyone encountered that?
I am, and was on latest OOS with stock kernel, latest TWRP blu_spark (the stock one gives me QUALCOMM CrashDump when trying to boot from fastboot in it), rooted with magisk (latest 18.1) and using magisk custom rom on top of stock (XXX_nolimits, latest).
Any of you encoutered this issue?
Thanks!
Click to expand...
Click to collapse
All you need to do is backup data. There are multiple threads explaining nandroid backup and restore. Just install OOS and TWRP, reboot recovery and flash all mods that you use, then restore data only and reboot.
Hi everyone,
I've been trying to get TWRP to stick for a while now, but still haven't been able to get it to install. A while ago I managed to flash Resurrection Remix using Lineage recovery which does work, but since Lineage recovery is quite limited, I really wanted to get TWRP to work. Since TWRP 3.5.0 released yesterday, I gave it another shot hoping that they fixed the issue, to no success.
I can get into TWRP just fine by temp booting it with fastboot, but after flashing the installer zip, any recovery that was previously installed gets wiped and the device will reboot when trying to get into recovery. I can still boot my phone otherwise.
The steps I took to get to this point:
Unlocked bootloader
fastboot boot twrp.img
Decrypt using screen pattern (successfully)
Flashed twrp installer zip (no error messages, process finishes successfully)
Reboot into recovery (both from twrp and bootloader at a later point)
Things I've tried:
Use a different TWRP version. Same problem as described above on both 3.4.x and 3.5.x, can't get it to decrypt on lower versions due to Android 10.
Install to recovery ramdisk, this just breaks things even more, probably because it's an A/B device?
Try a different recovery. Lineage recovery works just fine, but it's very very limited. Would really like to get TWRP working.
Trying to flash the zip results in no error messages, but any previously installed recovery gets wiped and magisk is uninstalled, which leads me to believe that it has done at least something to the boot img.
Thank you in advance.
EDIT 25.02.2021:
- Attached TWRP log
EDIT 12.03.2021:
- Log didn't want to attach, they can be found here: https://pastebin.com/awnhHDBU
Same question here. It seems that you can only boot from TWRP, not install it.
Tried installing again today, to no avail. However, I was smart enough to save the log this time. I have attached it to the main post, would be much appreciated if someone could check it out.